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

Secrets not found if I use the drop down secrets option #47

Open
jhkang-esnet opened this issue Jan 13, 2025 · 2 comments
Open

Secrets not found if I use the drop down secrets option #47

jhkang-esnet opened this issue Jan 13, 2025 · 2 comments

Comments

@jhkang-esnet
Copy link

I've noticed that the chart fails to install when the user uses the cloud credential name for the credentials in questions.yaml like so:

https://imgur.com/a/phHaS9w

It can correctly identify the corresponding cloud credential id but it still fails to apply anyways. I've looked at th cluster chart and the variable injection looks reasonable to me. I've gotten around this by hard-coding the credential id (I'd prefer not to) in a secret repo. Do you have any guidance around this issue?

@zackbradys
Copy link
Member

Hey @jhkang-esnet,

It looks like the image was deleted or I’m unable to to access it, either way, to answer your question on the questions.yaml… right now it is not working so any issues you encounter are from the fact that we haven’t updated it to account for the complete overhaul we did last year.

It is on the list of things we want to update and once we update it, it should be relatively easy to maintain and support going forward. Here’s the related open issue for it Issue #19!

@pknomad
Copy link

pknomad commented Jan 14, 2025

Hey @zackbradys

Thanks! I'm happy to contribute and validate on #19 when the fix is implemented. On an unrelated note - do you have a handy example of cilium values that work with Rancher Templates? If there isn't, I'm also happy to contribute in that space. I've also noticed using the UI often means RKE2 upstream cilium gets used but specifying cilium in YAML here means vanilla cilium gets used instead (I guess I should have expected as much).

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

No branches or pull requests

3 participants