This message was deleted.
# general
a
This message was deleted.
c
the controller installs them itself when it starts up, if they are missing
if you want to install them by hand you can find them in the system-upgrade-controller project release artifacts on GH
a
Ah, cool - thanks!
Follow-up question: I noticed it installs it's resources in cattle-system. Is there any point in installing the Helm chart outside of that namespace?
Well, the answer seems to be that one can't install the helm release there specifically. But then the plans have to be created in the cattle-system namespace as well?
Ok, hammered out the kinks and got it to work. Plans in
cattle-system
and with updated service account name.
c
the SUC can be deployed to watch plans in all namespaces, or only specific ones. I’m not sure what Rancher does by default.
if that wasn’t set it would watch all
a
Well the deployment is hardcoded to cattle-system so I'm not sure how I would set that to something else?
c
That one is yeah. People also run it standalone. It is covered in the k3s docs.
a
Yep, thanks for your help as always Brad 🙇