Description
Default kyma-gateway uses local.kyma.dev domain. That domain is not resolved inside the cluster. The domain should point to istio-ingressgateway.istio-system.svc.cluster.local instead of 127.0.0.1.
Coredns service supports overrides that can be used to modify the default coredns config map in the kube-sysstem namespace.
See: https://github.com/k3s-io/k3s/pull/7583
Description Default kyma-gateway uses local.kyma.dev domain. That domain is not resolved inside the cluster. The domain should point to
istio-ingressgateway.istio-system.svc.cluster.local
instead of127.0.0.1
.Expected result
Actual result
Solution
Coredns service supports overrides that can be used to modify the default coredns config map in the kube-sysstem namespace. See: https://github.com/k3s-io/k3s/pull/7583
This is a bash script with the solution:
Remarks DNS resolution worked before modularization with this code: https://github.com/kyma-project/cli/blob/main/internal/coredns/coredns.go But the solution proposed here is more clean (assuming it is applied by api-gateway operator).
PR