Skip to content
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

Closed
mdemri opened this issue Mar 27, 2024 · 9 comments
Closed

Can't pull rancher/system-upgrade-controller:latest image #332

mdemri opened this issue Mar 27, 2024 · 9 comments

Comments

@mdemri
Copy link

mdemri commented Mar 27, 2024

                         node.kubernetes.io/unreachable:NoExecute op=Exists for 300s                                                                                                                        │

│ Events: │
│ Type Reason Age From Message │
│ ---- ------ ---- ---- ------- │
│ Normal BackOff 3m58s (x282 over 69m) kubelet Back-off pulling image "rancher/system-upgrade-controller:latest"

@holooloo
Copy link

the same

@lloesche
Copy link
Contributor

lloesche commented Apr 8, 2024

Rancher got rid of the latest tag. You now need to specify the version, like.

system_upgrade_controller_manifest_url: https://raw.githubusercontent.com/rancher/system-upgrade-controller/v0.13.4/manifests/system-upgrade-controller.yaml

which then references e.g. image: rancher/system-upgrade-controller:v0.11.0

@manfredipist
Copy link

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.

kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/system-upgrade-controller.yaml

@vitobotta
Copy link
Owner

I am planning to fix this in the next release this coming week.

@vitobotta
Copy link
Owner

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.

@creib
Copy link
Contributor

creib commented Jun 2, 2024

Hi @vitobotta already an idea, when the new release is comming?

@vitobotta
Copy link
Owner

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.

@vitobotta
Copy link
Owner

rc1 of v2 is now available, can anyone help with testing? see #385 for details.

@vitobotta
Copy link
Owner

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants