Kubernetes Ingress Controllers

For security reasons it is not a good practice to create individual load balancers for each service. The safer way is to create one application load balancer outside of the cluster and launch ingress controller NGINX containers to proxy the traffic to the individual services. Ingress “Ingress exposes HTTP and HTTPS routes from outside the […]

Kubernetes Deployments

You only need a deployment to launch a container in Kubernetes. Deployments tell Kubernetes what container to run by specifying the Docker image name and tag spec: template: spec: containers: – image: when to pull the image from the registry spec: template: spec: containers: imagePullPolicy: If the image is always rebuilt with the same version, […]

Working with Kubernetes in enterprise settings

How many Kubernetes clusters do I need? Clusters First, we want to separate the non-production and production environments: Create two Kubernetes clusters for every application or application suite. One for pre-production and one for production. Namespaces We also want to separate each non-production and production like environment. Kubernetes offers namespaces to create segregated areas, resources […]

Kubernetes Services

Kubernetes Services route traffic across a set of pods. The service specifies how deployments (applications) are exposed to each other or the outside world. Service types The service type specifies how the deployment will be exposed ClusterIP The ClusterIP service is only visible within the cluster. To expose the pod to other services in the […]

Docker Swarm volumes

Containers are ephemeral. Containers live entirely in memory, so even if the container is set up with automatic restart, the new container will not have access to the data created inside of the old container. To save persistent data of Docker containers we need to create volumes that live outside of the ephemeral containers. Don’t […]