Cloud Diary

Kubernetes Ingress

Nayan Tank's photo
Nayan Tank
·

3 min read

Kubernetes Ingress

Table of contents

Kubernetes Ingress is an API object that provides an entry point for external traffic into the Kubernetes cluster. In other words, it is a way to expose your Kubernetes services to the outside world, by defining rules that determine how incoming traffic should be routed to different services within the cluster.

With Kubernetes Ingress, you can define a single point of entry for all incoming traffic, rather than exposing each service individually. This allows you to simplify your network configuration, and to manage and scale your applications more easily.

Kubernetes Ingress supports a range of routing and load balancing options, including HTTP, HTTPS, TCP, and UDP traffic. It also allows you to define SSL certificates, set up virtual hosts, and configure path-based routing.

To use Kubernetes Ingress, you typically need to set up an Ingress controller, which is responsible for implementing the rules defined in the Ingress resource. There are several Ingress controllers available, including NGINX, Traefik, and Istio.

Advantages of Kubernetes Ingress:

  1. Single point of entry: Ingress allows you to expose multiple services with a single IP address and hostname, simplifying network configuration and management.

  2. Routing and Load Balancing: Ingress provides flexible routing rules and load balancing for incoming traffic, enabling you to distribute requests to different backend services based on path, hostname, or other criteria.

  3. SSL/TLS termination: Ingress supports SSL/TLS termination, allowing you to encrypt traffic between clients and your cluster.

  4. Security: Ingress can also provide an additional layer of security by hiding the underlying service endpoints and preventing direct access to them.

  5. Scalability: Ingress is scalable and can handle large amounts of incoming traffic, making it suitable for high-traffic applications.

Disadvantages of Kubernetes Ingress:

  1. Complexity: Setting up and configuring Ingress can be complex, especially if you are new to Kubernetes. It requires knowledge of Kubernetes networking, routing, and load balancing concepts.

  2. Ingress Controller dependency: In order to use Ingress, you need to have an Ingress controller deployed in your cluster. This introduces an additional layer of complexity and may require additional resources.

  3. Limited Protocol Support: Ingress only supports HTTP, HTTPS, TCP, and UDP protocols, which may not be sufficient for certain use cases.

  4. Latency: Ingress routing can introduce additional latency, which may affect the performance of your application.

  5. Debugging and Troubleshooting: Debugging issues related to Ingress can be challenging, especially when dealing with complex routing rules and multiple services.

Example

Deployment.yml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 3
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80

Service.yml

apiVersion: v1
kind: Service
metadata:
  name: nginx-service
spec:
  selector:
    app: nginx
  ports:
  - name: http
    port: 80
    targetPort: 80

Ingress.yml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: nginx-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - http:
      paths:
      - path: /nginx
        pathType: Prefix
        backend:
          service:
            name: nginx-service
            port:
              name: http
KubernetesDevopskubernetes ingressTrainWithShubham