Kubernetes Ingress deployment strategies¶

Kubernetes Ingress deployment strategies encompass the methods and tools used to manage external access to services within a cluster, typically focusing on implementations like the NGINX Ingress Controller^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Deployment Methods¶

Strategies for deploying Ingress controllers often depend on the underlying cluster infrastructure^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. For local development environments such as Docker Desktop, specific deployment configurations are required to ensure compatibility^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Helm Package Manager¶

One common strategy is utilizing the Helm package manager to deploy the ingress-nginx controller^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. This approach simplifies the installation and management process by using a predefined chart from the official Kubernetes ingress-nginx repository^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

A typical Helm deployment command involves specifying the release name, chart location, and namespace^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]:

[Helm](<./helm.md>) upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace

Direct Manifest Application¶

Alternatively, administrators can deploy the controller by directly applying static manifest files^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. These files contain the necessary definitions for the controller, services, and associated RBAC rules^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

This method can be performed by fetching resources directly from the project's source repository or by applying local configuration files^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]:

[kubectl](<./kubectl.md>) apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.3.1/deploy/static/provider/cloud/deploy.yaml

[kubectl](<./kubectl.md>) apply -f ./deploy.yaml

Verification¶

After deploying the Ingress Controller, it is standard practice to verify the installation by applying a test resource^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. This confirms that the controller is routing traffic correctly within the cluster^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Sources¶

^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]