-
Notifications
You must be signed in to change notification settings - Fork 5
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 client cert with wrong SAN #18
Comments
Yeah I noticed that too while going through the ETCD Controller code, the SAN is set to be the secret name here: https://github.com/storageos/etcd-cluster-operator/blob/main/controllers/etcdcluster_controller.go#L240 Which I found odd, but my cluster worked fine even with the SAN looking wrong. It should be something along the lines of:
|
Hey @Arau - I can see the symptoms you describe (log lines seem to lead to this code) and I can confirm that the certificate SAN is I'm curious about the Ondat cluster not being able to connect - do you see any other log lines, perhaps in the API manager or scheduler? Are any pods NotReady? |
Hi, I executed the installation of charts with the umbrella and I see the issue as the Ondat pods can't connect to Etcd. Etcd logs indicating Then I executed the installation with the etcd chart first and then the ondat-operator. The result is the same. I fixed in the cluster by copying the contents of the secret In my values I put
I'm thinking if it is possible that the tests didn't have the |
I've been using etcd without the Another thought - did you uninstall/reinstall on the same cluster? I've noticed that the
|
We've pushed a new version, please re-test and let me know whether that resolves the issue! |
@Arau could you please review this issue? Thank you :) |
The Ondat cluster can't connect to etcd due to a
This is happening because the certificate in the
storageos-etcd-secret
has the following SAN definitionThe DNS field
storageos-etcd-secret
should match the DNS name:*.storageos-etcd.storageos-etcd
The text was updated successfully, but these errors were encountered: