Replies: 2 comments 3 replies
-
|
Beta Was this translation helpful? Give feedback.
3 replies
-
Certs added to client-ca secret and above issue fixed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Team,
I have a cluster with below configuration.
configuration:
brokerCertChainAndKey:
secretName: aione-kafka2-listener-secret
certificate: tls.crt
key: tls.key
bootstrap:
annotations:
service.beta.kubernetes.io/azure-load-balancer-internal: "true"
alternativeNames:
- watchtower-nprd-kafka.att.com
brokers:
- broker: 0
annotations:
service.beta.kubernetes.io/azure-load-balancer-internal: "true"
external-dns.alpha.kubernetes.io/hostname: watchtower-nprd-kafka-0.att.com
advertisedHost: watchtower-nprd-kafka-0.att.com
the brokercertificate used here is having different common name(watchtower.web.att.com) as compared to broker/bootstrap name(watchtower-nprd-kafka.att.com).
kubectl get secret aione-kafka1-listener-secret -o 'jsonpath={.data.tls.crt}' -n aione-dev | base64 -d | openssl x509 -subject -issuer -startdate -enddate -noout
subject=C = US, ST = Texas, L = Dallas, O = "Company", CN = watchtower.web.att.com
issuer=C = US, O = DigiCert Inc, CN = DigiCert Global G2 TLS RSA SHA256 2020 CA1
notBefore=May 17 00:00:00 2021 GMT
notAfter=May 25 23:59:59 2022 GMT
i have done this because i want to re-use same broker certs for many clusters.
so now i have client certs signed by digicerts. my client is failing with attached error. i havent imported ca.certs into client truststore as both client and server certs signed by same CA
any help is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions