Repository navigation
Remove dependency on external DNS configuration for internal kubernetes API requests #241
Closed as not planned
Description
When the user does not have the correct DNS record for the tenant Kubernetes API, attempting to read logs from the cluster results in the following error:
Error from server (InternalError): Internal error occurred: Authorization error (user=kube-apiserver-kubelet-client, verb=get, resource=nodes, subresource=proxy)
Current Workaround
To address this issue temporarily, I updated the CoreDNS configuration in the management cluster:
rewrite name dashboard.example.org root-ingress-controller.tenant-root.svc.cozy.local
rewrite name grafana.example.org root-ingress-controller.tenant-root.svc.cozy.local
rewrite name kubernetes-test.example.org root-ingress-controller.tenant-root.svc.cozy.local
After restarting Kamaji, the logs started working correctly.
I think we need to find a permanent solution to remove the dependency on correctly configured DNS records, at least for requests originating from within the cluster. This will ensure that internal API requests function correctly regardless of the external DNS configuration.
Activity
[-]Remove Dependency on Correct DNS Configuration for Internal Kubernetes API Requests[/-][+]Remove dependency on external DNS configuration for internal kubernetes API requests[/+]dosubot commentedon Oct 18, 2025
Hi, Andrei Kvapil (@kvaps). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!