How is pod separation organized in Kubernetes considering domains when configuring Nginx?

In Kubernetes, to organize pod separation by domains when configuring Nginx, the usual approaches are:

• Namespaces — logical separation of resources within the cluster. Each namespace can contain its own pods and services.

• Ingress with rules based on domains (host), which direct traffic to the appropriate services in specific namespaces.

Example of configuring Ingress with Nginx for different domains:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
  namespace: default
spec:
  rules:
  - host: app1.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: app1-service
            port:
              number: 80
  - host: app2.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: app2-service
            port:
              number: 80

Here, the Nginx Ingress controller directs requests to different services depending on the domain. Each service is associated with pods in the corresponding namespace or with specific labels.

Thus, pod separation by domains is achieved through:

• Using namespaces for isolation
• Configuring Ingress with host-based rules
• Labeling pods and services for precise routing

This allows flexible management of access and traffic routing in Kubernetes using Nginx.