Ingress: Effortless External Access to Your Services

Checking Ingress Details
To inspect details about Ingress resources, use the following commands:

kubectl get ingress
kubectl describe ingress <ingress-name>

Modifying Ingress Configuration
Edit the configuration of an existing Ingress resource:

kubectl edit ingress <ingress-name>

Applying Ingress Configuration
Apply the configuration defined in an Ingress YAML file:

kubectl apply -f <ingress.yaml>

Setting Up Ingress

Setting up Ingress involves the following components, all residing in the same namespace:

Ingress Controller (Deployment)
: Responsible for fulfilling Ingress rules.

Node Port Ingress Service:
Enables access to the Ingress controller from outside the cluster.

Config Map:
Configures various parameters for the Ingress controller.

Ingress Controller Initialization
Unlike other controllers, Ingress controllers do not start automatically. They require manual deployment. Kubernetes supports various Ingress controllers for different cloud providers, such as AWS, GCE, and nginx.

Ingress Resource Rules
The Ingress resource, defined with the type 'ingress', resides in a different namespace from the application (deployment) and the service (for accessing the deployment). The Ingress resource specifies the rules, and the Ingress controller ensures their fulfillment.

Enhance your Kubernetes cluster with Ingress, providing a seamless way to access your services from the external world.

Happy Kuberneting!