Skip to content
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

Explicit caBundle value makes using terraform to manage katib challenging #2367

Closed
vihangm opened this issue Jun 20, 2024 · 0 comments · Fixed by #2368
Closed

Explicit caBundle value makes using terraform to manage katib challenging #2367

vihangm opened this issue Jun 20, 2024 · 0 comments · Fixed by #2368
Labels

Comments

@vihangm
Copy link
Contributor

vihangm commented Jun 20, 2024

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 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants