Skip to content
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.

x509: certificate is valid for x, y, z, not a #123

Open
webwurst opened this issue Mar 19, 2019 · 1 comment
Open

x509: certificate is valid for x, y, z, not a #123

webwurst opened this issue Mar 19, 2019 · 1 comment

Comments

@webwurst
Copy link

At first, thanks for this great project! It works fine for me, except for this one tiny issue that the created kubeconfig is valid for three internal IP addresses of the cluster and not for the external one. I am not sure if I am making some mistake here or if this already configurable. But it would be cool if I could add another valid IP for the created certificate. Or maybe the address that is set in apiServerURL?

Thanks for any advise!

@gmwingard
Copy link

What are you using to deploy k8s? This is unrelated to gangway by the way.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants