-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Can't pull rancher/system-upgrade-controller:latest image #332
Comments
the same |
Rancher got rid of the
which then references e.g. |
It's also mandatory to apply the whole manifest after cluster has been created otherwise some clusterRole bindings will go missing and system-upgrade-controller pod won't go up.
|
I am planning to fix this in the next release this coming week. |
This seems related to #327. As said in that issue I have fixed this on main (not released yet). If you could test it as well I would appreciate. |
Hi @vitobotta already an idea, when the new release is comming? |
I am having some trouble to find the time at the moment because I have been promoted to a new role with more responsibilities and am having to prepare some stuff that takes time. I will try to work on it this coming weekend. |
rc1 of v2 is now available, can anyone help with testing? see #385 for details. |
Various improvements have been made in v2, which will be released probably next weekend. If you still have problems with v2 (currently rc4) then please open a separate issue with details on v2 :) |
│ Events: │
│ Type Reason Age From Message │
│ ---- ------ ---- ---- ------- │
│ Normal BackOff 3m58s (x282 over 69m) kubelet Back-off pulling image "rancher/system-upgrade-controller:latest"
The text was updated successfully, but these errors were encountered: