k8s_gateway is a CoreDNS plugin that resolves all types of external Kubernetes resources.
It will gather all domains from all services, ingresses, and HTTPRoutes resources and create a DNS record for each of them, corresponding to the service IPs. This ensures that all external resources are resolved from within the cluster, and traffic is not leaving the cluster.
Most people deploy the k8s_gateway together with CoreDNS and call the Helm Release 'k8s-gateway'. This can be supplimenting along side the kube-dns or default CoreDNS from k3s.
k8s-gateway from ori-edge is more popular with 66 repositories.
Install with:
helm repo add k8s-gateway oci://ghcr.io/home-operations/charts-mirror/k8s-gateway
helm install k8s-gateway k8s-gateway/k8s-gateway -f values.yamlSee examples from other people.
| Name | Repo | Stars | Version | Timestamp |
|---|---|---|---|---|
| k8s-gateway | ahgraber/homelab-gitops-k3s | 90 | 3.2.0 | 7 days ago |
| k8s-gateway | samip5/k8s-cluster | 137 | 3.2.0 | 7 days ago |
| k8s-gateway | samip5/k8s-cluster | 137 | 3.2.0 | 2 months ago |
See the most popular values for this chart:
| Key | Types |
|---|---|
domain (15) ${SECRET_DOMAIN} | string |
| string | |
| number | |
service.type (15) LoadBalancer | string |
service.annotations."lbipam.cilium.io/ips" (9) 10.100.151.31 | string |
| string | |
service.annotations."metallb.universe.tf/loadBalancerIPs" (1) ${METALLB_K8S_GATEWAY_ADDR} | string |
| number | |
watchedResources[] (14) - HTTPRoute | string |
fullnameOverride (12) k8s-gateway | string |
image.pullPolicy (4) IfNotPresent | string |
image.registry (4) ghcr.io | string |
image.repository (4) k8s-gateway/k8s_gateway | string |
image.tag (4) 1.3.0 | string |
filters.ingressClasses[] (3) - internal | string |