-
Notifications
You must be signed in to change notification settings - Fork 60
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 Handshake error from <host>:<port> remote error: tls: bad certificate #203
Comments
what namespace did you install the operator in? |
I installed the operator in a namespace called “ldap-groupsync”. I created this namespace and installed the operator. Thanks. |
Thats the issue. There is a challenge currently when using a namespace other than No current workaround yet but still investigating |
Thank You. |
Facing same issue. Is there any work around to use namespace other than group-sync-operator. |
Hi, We installed the operator from OpenShift OperatorHub. In controller manager pod's log, we keep getting below error message when we set namespace label openshift.io/cluster-monitoring: "true"
TLS Handshake error from : remote error: tls: bad certificate
Please let me know what would be the issue and how to resolve this.
Thanks.
The text was updated successfully, but these errors were encountered: