Ingress controller configuration¶

Ingress controller configuration involves setting up a specific component within a kubernetes cluster that manages inbound traffic routing. While the cluster typically has a default routing mechanism enabled, customizing the controller allows for specific traffic handling rules and integration with different load balancers^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md].

Default Configuration¶

When a kubernetes cluster is provisioned, an Ingress controller is generally enabled by default^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md]. The default implementation typically utilizes the NGINX Ingress Controller^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md].

To verify the default configuration or view the running services, administrators can use the command kubectl get svc -n ingress-nginx^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md].

Implementation¶

The core function of the Ingress Controller is to listen for changes in Ingress resources (defined in YAML files) and update the backend load balancer configuration accordingly^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md].

Related Concepts¶

• Ingress
• kubernetes
• Blue/Green Deployment
• A/B Testing Deployment

Sources¶

^[400-devops__06-Kubernetes__k8s-ithelp__Day11__README.md]