You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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!
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).
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?
The text was updated successfully, but these errors were encountered: