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
I tried to enable rancher before, but then realized that my k3s is to new. By now it should be supported, so I tried to re-enable rancher.
After re-enabling rancher by setting enable_rancher to true, nothing happend except for k3s_kustomization_backup.yaml being updated.
My feeling is that it should have installed rancher using helm, but helm ls --all-namespaces does not show it. kubectl get helmcharts.helm.cattle.io --all-namespaces also does not contain anything rancher-related.
@hco We use the rancher helm controller which has CRDs from within the cluster. Just do kubectl get crds -A | grep helm to find them, query them, and delete the ones for rancher.
Description
I tried to enable rancher before, but then realized that my k3s is to new. By now it should be supported, so I tried to re-enable rancher.
After re-enabling rancher by setting
enable_rancher
totrue
, nothing happend except for k3s_kustomization_backup.yaml being updated.My feeling is that it should have installed rancher using helm, but
helm ls --all-namespaces
does not show it.kubectl get helmcharts.helm.cattle.io --all-namespaces
also does not contain anything rancher-related.Kube.tf file
Screenshots
No response
Platform
mac
The text was updated successfully, but these errors were encountered: