Strimzi Kafka on GKE - LetsEncrypt cert(secret) getting generated with name+randomtext #10793
karanalang
started this conversation in
General
Replies: 1 comment
-
I don't think that this question is related to Strimzi. It's just about how cert-manager and how it works and also it's not integrated within Strimzi yet. |
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
-
Hello -
I'm using terraform to create a GKE cluster & deploy Strimzi Kafka(v0.38), and the script is using ACME protocol to get certificate from LetsEncrypt,
and running into issues wherein the secret being created (when deploying certificate.yaml) is created with random string attached to the secret name.
Script does the following :
creates a GKE cluster (version - 1.30.5-gke.1355000)
Installs cert-manager in namespace cert-manager,
version of cert-manager - v1.13.2
Command :
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.13.2/cert-manager.yaml
Install External-DNS (in namespace - kafka)
creates ClusterIssuer for prod & staging
creates Certificate (in namespace - kafka)
Finally, it deploys Strimzi kafka (v0.38)
Here is the certifcate.yaml & values.yaml for the helm chart
Describing the cert shows error that the Cert is not ready, since the required secret (versa-kafka-poc-tf2-lets-encrypt) is not available, instead the secret is created with a random string attached to the name:
Question is - why is the secret getting created with a random string added to the secret name ?
How to debug/fix this ?
tia!
Beta Was this translation helpful? Give feedback.
All reactions