Kubernetes Cluster: Installed Nginx-Ingress Controller, Maintained Nginx, Manifests

Overview

This article provides a detailed context on the topic of Kubernetes Cluster, specifically focusing on the installation and maintenance of the Nginx-Ingress Controller, as well as the use of the "ingressClassName" in manifests for applications.

Key Concepts

• Nginx-Ingress Controller: A popular open-source software that acts as an edge router, load balancer, and HTTP cache for applications deployed on Kubernetes.
• Manifests: YAML or JSON files that define the desired state of Kubernetes objects, such as deployments, services, and ingresses.
• "ingressClassName": A field in manifests that allows you to specify the class name of the Ingress resource that will be created by the Nginx-Ingress Controller.

Detailed Context

To begin, ensure that your Kubernetes cluster has the Nginx-Ingress Controller installed and running. This can typically be done by deploying the Nginx-Ingress Controller using Helm or Kustomize, or by using a managed Kubernetes service that includes the Nginx-Ingress Controller.

Once the Nginx-Ingress Controller is up and running, you can maintain it by keeping its Helm chart or Kustomization files up-to-date. This ensures that the Nginx-Ingress Controller stays compatible with the latest versions of Kubernetes and the Nginx web server.

When creating manifests for your applications, you can utilize the "ingressClassName" field to specify the class name of the Ingress resource that will be created by the Nginx-Ingress Controller. This allows you to customize the behavior of the Ingress resource for your specific application needs.

Code Blocks

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-app-ingress
  annotations:
    kubernetes.io/ingress.class: my-nginx-ingress-class
spec:
  rules:
  - host: my-app.example.com
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: my-app-service
            port:
              number: 80
    

In the example above, the "my-nginx-ingress-class" annotation specifies the class name of the Ingress resource that will be created by the Nginx-Ingress Controller. This allows you to customize the behavior of the Ingress resource for your specific application needs.

References

• Books: Kubernetes: Up and Running (O'Reilly)
• Articles: Ingress, Ingress Controllers
• Online Resources: Helm, Kustomize