Ingress testing workflow¶

The Ingress testing workflow is a procedure used to verify that an Ingress Controller—specifically NGINX within a Kubernetes environment on Docker Desktop—is functioning correctly after installation^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Prerequisites¶

Before testing can commence, the Ingress Controller must be deployed to the cluster^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. This can be achieved using helm to install the ingress-nginx chart into a dedicated namespace^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. Alternatively, the controller can be deployed using kubectl to apply a static manifest, either sourced remotely from the project repository or a local deploy.yaml file^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Execution¶

Testing is performed by applying a specific test configuration to the cluster^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]. The standard command to initiate this test is kubectl apply -f ./test-nginx-ingress.yaml, which deploys the resources necessary to validate routing and connectivity^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md].

Sources¶

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