This message was deleted.
# general
a
This message was deleted.
j
I ran into an issue where if i used the UI to update it, it would blank it out. I instead edited the configuration yaml directly using Kubectl
s
we where trying to add nodes to cluster node was stuck on “waiting for noderef” then while checking the plan we found the plan was showing no data. while checking using CLI we are getting 0 data. rancher is responsible for creating this secret right?
j
yes i beleive so. so when you performed your upgrade/add nodes did you edit the config of that cluster through the ui and then click save. That is the pattern i had an issue with, just clicking the plus on the outer cluster area was good enough, any configuration changes to the cluster I now perform through the YAML's directly via kubectl
s
Now we are trying to debug the issue by creating a new cluster and we are facing the issue in the 1'st node itself. yes we are running on a airgap environment we have couple of registry rewrite and other config so we are doing this creation from UI
did you faced this issue on older versions?
j
2.7.4 using the UI was particularly pretty buggy when editing helm charts. But we stopped editing using the UI in 2.6.X because of consistent issues with the lookup function that happens on the page load
in our case we had deleted the original VM image and when we just went in to do a config update, it tried to reprovision the entire cluster to the "First VM" it saw back from the VM provider vs leaving the old value of the template in the config
Too easy to nuke a cluster in standard maintenance
we are working at converting all of our Rancher provisioned clusters over to a custom Helm chart to manage the values.
s
ok let me check with kubectl and try. in our environment everything is airgap we are deploying RHEL machines and then using custom rke2 cluster option.
💯 1
ok i think we need to move yaml files for rms. we where planning to manage other config using terraform. let’s see. Thanks 🙂
j
We prefer the native kubernetes way, and not requiring additional tools (terraform) to perform maintenance
👍 1