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

Get cacert into workload cluster #188

Open
jschoone opened this issue Dec 4, 2024 · 3 comments
Open

Get cacert into workload cluster #188

jschoone opened this issue Dec 4, 2024 · 3 comments
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling

Comments

@jschoone
Copy link
Contributor

jschoone commented Dec 4, 2024

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Kubernetes version: (use kubectl version)
  • OS (e.g. from /etc/os-release):
@jschoone jschoone added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Dec 4, 2024
@garloff
Copy link
Member

garloff commented Jan 12, 2025

Half the solution is to add --set cacert="$(cat /path/to/single-ca-cert.pem)" on the helm call.
This gets capo to work with the custom CA.

Unfortunately not OCCM. OCCM not coming up still leaves you with a pretty disfunctional cluster.

@garloff
Copy link
Member

garloff commented Jan 12, 2025

To get OCCM to work, we probably need to tweak ca-file AND ensure we somehow get the secret mounted into OCCM's file system so we can reference it. That probably means tweaking the OCCM pod deployment file ...
(A working workaround is to change cloud.conf and add in tls-insecure=true in the helm _helpers.tpl -- not recommended of course!)

@garloff
Copy link
Member

garloff commented Jan 13, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling
Projects
Status: Backlog
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants