Internal Ingress Controller

The Internal Ingress Controller in KubeDNA handles all in-cluster application traffic routed through a VPN connection. It is designed for applications that do not require access to the public internet, ensuring a secure internal-only routing layer.

🔧 Features

Ingress Class: nginx-intern
Scope: Only accessible within the VPN
Deployment: Automatically installed by KubeDNA during cluster setup
Purpose: For internal services like APIs, back-office tools, or monitoring dashboards that should not be exposed externally

example:

YAML

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: sample-nginx-extern-ingress
  namespace: default
spec:
  ingressClassName: nginx-intern
  rules:
  - host: example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: my-service
            port:
              number: 80