Explicit caBundle value makes using terraform to manage katib challenging
Closed this issue · 0 comments
vihangm commented
What happened?
We use terraform to manage a lot of our clusters and so having the caBundle in the webhooks set to Cg== causes issues since it later gets replaced but that makes terraform unhappy since the cluster state no longer matches the spec.
The caBundle has been optional since Kubernetes v1.13 (see kubernetes/kubernetes#69590) so having it unset is better than setting it to the newline char.
What did you expect to happen?
Unsetting the caBundle fixes the issue since terraform treats it as a computed field.
Environment
Kubernetes version: v1.30.1-gke.1156000
Katib controller version: v0.16.0
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍