-
Notifications
You must be signed in to change notification settings - Fork 11
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
Support multiple alternative names in the API certificate #87
Comments
That throws an error for me
|
@rothgar you have to use the e.g.
|
Thanks for pointing that out. I tried again with
This time I tried signing it with my tailnet DNS and local lan DNS but if I download the kubeconfig and change the host it fails.
And openssl doesn't have the alt names
The container logs look fine though
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
K2D_ADVERTISE_ADDR
currently accepts a single option to sign the certificate. It would be useful to be able to sign alternative names or IP addresses for certificates to be trusted based on IP addresses or aliases.For example, I would like to be able to use the hostname of the machine, IP address for the LAN, and IP address and hostname from my tailscale network.
The text was updated successfully, but these errors were encountered: