brandond
commented
9 months ago I can't reproduce this.
brandond@dev01:~$ kubectl get node -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k3s-server-1 Ready control-plane,master 6m36s v1.26.4+k3s1 172.17.0.4 <none> K3s dev 5.19.0-1019-aws containerd://1.6.19-k3s1
brandond@dev01:~$ kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml
namespace/system-upgrade created
serviceaccount/system-upgrade created
clusterrolebinding.rbac.authorization.k8s.io/system-upgrade created
configmap/default-controller-env created
deployment.apps/system-upgrade-controller created
brandond@dev01:~$ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system local-path-provisioner-76d776f6f9-fhdmj 1/1 Running 0 26s
kube-system coredns-59b4f5bbd5-p4vwz 1/1 Running 0 26s
kube-system svclb-traefik-6c3a9382-qfzfc 2/2 Running 0 19s
kube-system helm-install-traefik-crd-4q2kw 0/1 Completed 0 27s
kube-system helm-install-traefik-rsx42 0/1 Completed 1 27s
kube-system traefik-56b8c5fb5c-7sdkv 1/1 Running 0 19s
kube-system metrics-server-7b67f64457-5685l 1/1 Running 0 26s
system-upgrade system-upgrade-controller-5876667756-2ppqw 1/1 Running 0 8s
brandond@dev01:~$ kubectl apply -f -
apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
name: server-plan
namespace: system-upgrade
spec:
concurrency: 1
cordon: true
channel: https://update.k3s.io/v1-release/channels/stable
nodeSelector:
matchExpressions:
- key: node-role.kubernetes.io/control-plane
operator: In
values:
- "true"
serviceAccountName: system-upgrade
upgrade:
image: rancher/k3s-upgrade
plan.upgrade.cattle.io/server-plan created
brandond@dev01:~/go/src/github.com/k3s-io/k3s$ kubectl get job -n system-upgrade
NAME COMPLETIONS DURATION AGE
apply-server-plan-on-k3s-server-1-with-0e4e3f4e3f8b1e811d-f6e12 0/1 48s 48sDo you perhaps have something else deployed to your cluster that's blocking creation of the upgrade job? Have you tried increasing the verbosity of the system-upgrade-controller?
anon-software
Version
Platform/Architecture
Describe the bug
I followed the instructions at https://docs.k3s.io/upgrades/automated to set up the automated upgrades. For the initial configuration I specified only the control plane node upgrade plan. However no action appear to have been taken.
To Reproduce
The content of control.yml can be seen below. The controller and the plan have been loaded at this point, but nothing happened which you can see from the node versions.
Expected behavior
Based on the plan and the current version, I expected to see a job that would upgrade the control plane node to version 1.27. Or, if there is something wrong with my environment (for example, it has occurred to me that I might need more than one control plane node to stagger an upgrade), I would expect to see an appropriate message in the log, but there is nothing of interest in it:
Actual behavior
Nothing happened.
Additional context
There had been a similar bug report I found https://github.com/rancher/system-upgrade-controller/issues/90, but in that case the node selector in the plan was wrong. Here is what the plan looks in this case:
And the selector verification follows: