-
Notifications
You must be signed in to change notification settings - Fork 93
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
No generated jobs after submitting update plan on RKE2 cluster #217
Comments
Ok there seems to be an issue with the upgrade-controller and our proxy environment. When I exchange the line
with
in my update plan I get TCP I/O timeout messages when trying the rke2 channel url in the update-controller log. Why it doesn't happen when I specify a version directly is another topic, but I would assume our company proxy is not used by the update-controller. Is there a way to tell the update-controller to use a proxy or if need be a local registry? I don't think I'm the only one with a corporate proxy setup. |
I have the exact same issue. I do not have a proxy. Simply following the docs and when I do
but no jobs :
current version is
Maybe I am missing something ? Do I need to run an |
I had this same problem as well. |
Thanks, that was the issue! Well for me part of it. Nevertheless thanks a lot for your answer! |
Version
v0.10.0
Platform/Architecture
RKE2 v1.24.7 on SLES 15SP4 x86_64
Describe the bug
Deploying the system-upgrade-controller seems to work fine, but after submitting the update plan according to this dokumentation results in no update and no created update jobs.
kubectl -n system-upgrade get plans -o yaml
returns the two submitted update plans:click to expand
But all I get via
kubectl -n system-upgrade get jobs -o yaml
is an empty list:I deployed the update-controller with debug output enabled, the logs are of no real help to me. Maybe somebody can see something in them:
click to open
The controller reads the plan and seems to somehow accept it, but there is no job created and no update performed.
To Reproduce
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.10.0/system-upgrade-controller.yaml
kubectl apply -n system-upgrade -f update-plan.yaml
click to open update plan
Expected behavior
A list containing at least one planned update job or updated RKE2 nodes to the version specified in the plan.
Actual behavior
Plan seems to be accepted, but no jobs are being planned. No update to the desired K8s version.
Additional context
We are behind a corporate proxy, but containerd and RKE2 have been configured accordingly. There is no indicator to a connection issue in the logs either.
The text was updated successfully, but these errors were encountered: