Experiences on single node k3s? / Job does not get created

[3deep5me]

Hi Folks,

does somebody runs the upgrade-controller on a single node kubernetes?
I try to get the upgrade controller running in a most simple way. Without success...
Is it maybe not possible to upgrade single node clusters? It would be really thankful if somebody has an idea.
The Job does not get created.

Thats my configuration:
Plan

apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
  annotations:
    objectset.rio.cattle.io/applied: H4sIAAAAAAAA/4SRT2vjMBDFv8oyZ/9LbDaJYA85Lyx76n0sj2PV9khoxikl5LsXNSlNCm2OQu+939PTCTC4J4riPIOBJRwidlRYVJ2ocL48riCD0XEHBv5PyJDBTIodKoI5ATJ7RXWeJR19+0xWhbSIzt+kuGSH7Nt7/8IU88NxBANjLXf87Ndfx92ffdd5fhjBOBMYCJemj7US0CbDuLSUy6sozXDOYMKWph9fNKAMYKBvflfburdVv6YKq8266dsdYd/s6jVuqqZqabtZ2SqF3ne7pV/A+XX9pJVANuHtgMw0gYFBNYgpyyV0qFSkld7nySNNhELlVSqlKLYTQQZC8egs7a31C+u/C/4LK/v480RzMx6SJiLbgWI51vJZ6nx+CwAA//8HGnEXLQIAAA
    objectset.rio.cattle.io/id: ""
    objectset.rio.cattle.io/owner-gvk: k3s.cattle.io/v1, Kind=Addon
    objectset.rio.cattle.io/owner-name: plan
    objectset.rio.cattle.io/owner-namespace: kube-system
  creationTimestamp: "2024-08-02T16:36:21Z"
  generation: 1
  labels:
    objectset.rio.cattle.io/hash: f46083fc0f2e0a0724fb9eaf4932a7040be871c0
  name: plan
  namespace: system-upgrade
  resourceVersion: "801667"
  uid: b150ae3d-693f-4cb6-8dac-e3e6dd06c40b
spec:
  channel: https://update.k3s.io/v1-release/channels/stable
  serviceAccountName: system-upgrade
  upgrade:
    image: rancher/k3s-upgrade
status:
  conditions:
  - lastUpdateTime: "2024-08-02T16:37:01Z"
    reason: PlanIsValid
    status: "True"
    type: Validated
  - lastUpdateTime: "2024-08-02T16:36:21Z"
    reason: Channel
    status: "True"
    type: LatestResolved
  - lastUpdateTime: "2024-08-02T16:36:21Z"
    status: "True"
    type: Complete
  latestHash: 02dc404cdc0a069984e141372b1a51e2e9e94a356a5537c537900cad
  latestVersion: v1.30.3-k3s1

Logs

W0802 16:37:01.387522       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2024-08-02T16:37:01Z" level=info msg="No access to list CRDs, assuming CRDs are pre-created."
time="2024-08-02T16:37:01Z" level=info msg="Starting /v1, Kind=Node controller"
time="2024-08-02T16:37:01Z" level=info msg="Starting /v1, Kind=Secret controller"
time="2024-08-02T16:37:01Z" level=info msg="Starting batch/v1, Kind=Job controller"
time="2024-08-02T16:37:01Z" level=info msg="Starting upgrade.cattle.io/v1, Kind=Plan controller"

Labels

kubectl get node --show-labels
NAME         STATUS   ROLES                  AGE   VERSION        LABELS
oracle-arm   Ready    control-plane,master   29d   v1.29.6+k3s1   beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,kubernetes.io/arch=arm64,kubernetes.io/hostname=oracle-arm,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=true,node-role.kubernetes.io/master=true,node.kubernetes.io/instance-type=k3s

version output

$ k3s --version
k3s version v1.29.6+k3s1 (83ae095a)
go version go1.21.11