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

TLS Route Certificates need IP SANs when Deployed to same IP #73

Open
rclayton-the-terrible opened this Issue Oct 12, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@rclayton-the-terrible

rclayton-the-terrible commented Oct 12, 2018

I know this is not a NATS issue, but I wanted to point out an issue we are experiencing due to the nature of k8s deployments and the way the operator is currently configured.

Also, I'm not sure if this is related to #32

I'm using a wildcard CN *.nats-mgmt.nats-io.svc for the routes and when a cluster node is deployed with the same IP Address as another node, I receive the following error:

[1] 2018/10/12 18:46:42.988808 [ERR] 172.28.219.187:6222 - rid:4 - TLS route handshake error: x509: cannot validate certificate for 172.28.219.187 because it doesn't contain any IP SANs

I could add IP SANs to my certificate, but that seems crazy since the IP is unpredictable (and IP SANs can't use wildcards AFAIK).

Is there a strategy I'm missing? Perhaps we need an option to skip hostname verification? Or better yet, force deployment to different IPs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment