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

Allow generating admin kubeconfig (k3s.yaml) with server hostname instead of IP address #11173

Open
brandond opened this issue Oct 25, 2024 · 0 comments
Labels
kind/enhancement An improvement to existing functionality kind/feature A large new piece of functionality
Milestone

Comments

@brandond
Copy link
Member

brandond commented Oct 25, 2024

Add a CLI flag, env var, or something else that allows generating the admin kubeconfig with the server's hostname in the server URL, instead of the loopback address or bind address.

Originally posted in #11165 (comment):

@krisgeus
I can use sed to fix the kubeconfig bit I also need the servername as alias in the certificate (which the tls-san does correctly) I would expect the server to write out a valid config I can use without fiddling with it myself.

@brandond
Note that our docs have ALWAYS referenced changing the server address in the admin kubeconfig if you want to acccess the server from elsewhere: https://docs.k3s.io/cluster-access#accessing-the-cluster-from-outside-with-kubectl

@brandond brandond moved this from New to Accepted in K3s Development Oct 25, 2024
@brandond brandond added kind/feature A large new piece of functionality kind/enhancement An improvement to existing functionality labels Oct 25, 2024
@brandond brandond added this to the Backlog milestone Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement An improvement to existing functionality kind/feature A large new piece of functionality
Projects
Status: No status
Status: Accepted
Development

No branches or pull requests

1 participant