Ditching Docker Compose for Kubernetes

1

Docker Hub

The imagePullPolicy must be set to Never or IfNotPresent. It cannot be set to Always otherwise Kubernetes will attempt to pull the image from a remote registry like Docker Hub, and it would fail.

#Developer Tools #Web Servers #Web And Application Servers 306 social mentions

2

Helm.sh

Chances are the application's service might be a ClusterIP or LoadBalancer type when deployed to other Kubernetes clusters, or that the nodePort will have a different value in those clusters. You can get around this by templating your service definition in Helm, and having different service configurations for your local Kubernetes versus other Kubernetes clusters.

#Developer Tools #DevOps Tools #Containers As A Service 134 social mentions

3

Docker Registry 2.0

With Docker Compose I can build an image and run it with just one simple command docker-compose up --build, assuming I have my docker-compose files setup. What's the analogue of this with Kubernetes? When I build an image, how can Kubernetes pull it? Do I need a local Docker Registry to push my image to?

#Package Manager #Software Development #Sysadmin 21 social mentions