Closed onedr0p closed 3 years ago
are you installing this as a helm chart?
No, I am using this as a coredns plugin on my router.
it must be the RBAC issue then. your role + roleBinding look fine. Check that coredns itself is running with the home-dns
serviceAccount and in kube-system
namespace.
This instance of coredns w/ k8s_gateway is not running in my cluster. It is running on my router. The purpose of coredns on my router is to get the ingresses from my k8s cluster and serve them as dns records to my network.
oh yeah, sry, I've missed the fact that you're running outside of the cluster. can you share your corefile as well?
.:53 {
bind 192.168.1.1 127.0.0.1 ::1
errors
log
reload
loadbalance
prometheus :9153
cache
k8s_gateway domain.tld {
resources Ingress
ttl 30
kubeconfig /usr/local/etc/coredns/kubeconfig
fallthrough
}
forward . tls://1.1.1.1 tls://1.0.0.1 {
tls_servername cloudflare-dns.com
}
}
🤦🏼 PEBKAC issue, my kube api ip was hella wrong (off by one number) in the kubeconfig
Hi :wave:
I am running this and getting an error. My service account has the right access, unless I am missing something. Using the
kubeconfig
I mention below I can list ingresses and services just fine with kubectl.I can verify if I use a
kubeconfig
with full access it works fine.Error
RBAC
kubeconfig