Hostname based route using Nginx ingress controller

Ingress is a powerful feature in Kubernetes that allows you to control the access to your application services. It acts as a reverse proxy and routing layer for your microservices, allowing you to define rules and routes that determine how external clients can access your services.

Ingress is implemented as a Kubernetes resource, and it is typically deployed as a Kubernetes deployment or a DaemonSet. It is also possible to use an Ingress controller, which is a separate service that runs alongside your application and handles the actual routing and proxying of requests.

One of the main benefits of using Ingress is the ability to easily expose multiple services on a single IP address or hostname. This can be useful for microservices architectures, where you may have multiple services running on different ports or paths.

Ingress also allows you to define rules for routing requests based on various criteria, such as the hostname, path, or headers. This can be useful for implementing features such as load balancing, canary releases, and A/B testing.

Another benefit of ingress is that it can be configured to use different authentication and authorization methods. This means that you can secure your services by requiring clients to provide certain credentials or tokens before accessing your services.

Ingress can be integrated with various other Kubernetes resources and controllers, such as Services, Deployments, ConfigMaps and Secrets.

To use Ingress, you will need to deploy an Ingress controller, such as Nginx or Istio, and then define your Ingress rules in a Kubernetes YAML file. Here’s an example of an Ingress resource that routes requests to two different services based on the hostname

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
 name: my-ingress
 annotations:
 nginx.ingress.kubernetes.io/rewrite-target: /
spec:
 rules:
 - host: service1.example.com
 http:
 paths:
 - path: /
 pathType: Prefix
 pathRewrite: /
 pathBackend:
 service:
 name: service1
 port:
 name: http
 - host: service2.example.com
 http:
 paths:
 - path: /
 pathType: Prefix
 pathRewrite: /
 pathBackend:
 service:
 name: service2
 port:
 name: http

In this example, requests to service1.example.com will be routed to the “service1” service, while requests to service2.example.com will be routed to the “service2” service.

Ingress is a powerful and flexible feature that can help you to improve the security, scalability and reliability of your application services. It can be integrated with different types of Ingress controllers, and it provides a lot of flexibility in terms of routing and security.