Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove dependency on external DNS configuration for internal kubernetes API requests #241

Open
kvaps opened this issue Jul 27, 2024 · 0 comments

Comments

@kvaps
Copy link
Member

kvaps commented Jul 27, 2024

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)

https://stackoverflow.com/questions/54572775/kubectl-logs-f-gets-authorization-error/68355619#68355619

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.

@kvaps kvaps changed the title Remove Dependency on Correct DNS Configuration for Internal Kubernetes API Requests Remove dependency on external DNS configuration for internal kubernetes API requests Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant