Hi! I noticed something that looked a bit off duri...
# rke2
c
Hi! I noticed something that looked a bit off during an upgrade of a cluster, i was trying to find out where the status updates you see in the UI where actually coming from. The cluster object (CAPI), of a cluster being upgraded, looked like this when inspecting the status and the conditions:
Copy code
apiVersion: <http://cluster.x-k8s.io/v1beta1|cluster.x-k8s.io/v1beta1>
kind: Cluster
...
status:
  conditions:
  - lastTransitionTime: "2024-01-11T16:17:01Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-01-11T16:28:50Z"
    status: "True"
    type: ControlPlaneInitialized
  - lastTransitionTime: "2025-04-10T08:47:15Z"
    message: 'draining worker node(s) worker01:
      error draining machine worker01:
      error when evicting pods/"pod01" -n "my-app":
      global timeout reached: 10m0s'
    reason: Waiting
    status: Unknown
    type: ControlPlaneReady
  - lastTransitionTime: "2024-01-11T16:17:01Z"
    status: "True"
    type: InfrastructureReady
If i enumerated the object via the Rancher API (using a go lib i've created) i could get out information that the condition type that the message was added to is called
Updated
. But when checking the objects through
kubectl
it looks like it's appended to the
ControlPlaneReady
condition? I would expect the
Updated
condition type to be rendered as it's own item in the conditions list?