During today's meeting we had the question, why the bootcnode when created is in Staged and not in Booted desired stage
k get bootcnode -oyaml
apiVersion: v1
items:
- apiVersion: node.bootc.dev/v1alpha1
kind: BootcNode
metadata:
creationTimestamp: "2026-07-06T14:23:27Z"
generation: 1
name: worker
ownerReferences:
- apiVersion: node.bootc.dev/v1alpha1
blockOwnerDeletion: true
controller: true
kind: BootcNodePool
name: workers
uid: e611aec3-f8a4-47b7-8eeb-99cd78eed0b4
resourceVersion: "968"
uid: c538a582-8ca4-42cf-8036-670488ceb1f5
spec:
desiredImage: registry.cluster.local:5000/node@sha256:646a1b971d9bb3f2d3f2d43c63bcb721bcdd803a8db36d1e298dc4b828ba90b2
desiredImageState: Staged
[...]
How to reproduce
Create a cluster bink with a worker node and apply this yaml:
apiVersion: node.bootc.dev/v1alpha1
kind: BootcNodePool
metadata:
name: workers
spec:
nodeSelector:
matchLabels:
node-role.kubernetes.io/worker: ""
image:
ref: registry.cluster.local:5000/node:latest
During today's meeting we had the question, why the bootcnode when created is in Staged and not in Booted desired stage
k get bootcnode -oyaml apiVersion: v1 items: - apiVersion: node.bootc.dev/v1alpha1 kind: BootcNode metadata: creationTimestamp: "2026-07-06T14:23:27Z" generation: 1 name: worker ownerReferences: - apiVersion: node.bootc.dev/v1alpha1 blockOwnerDeletion: true controller: true kind: BootcNodePool name: workers uid: e611aec3-f8a4-47b7-8eeb-99cd78eed0b4 resourceVersion: "968" uid: c538a582-8ca4-42cf-8036-670488ceb1f5 spec: desiredImage: registry.cluster.local:5000/node@sha256:646a1b971d9bb3f2d3f2d43c63bcb721bcdd803a8db36d1e298dc4b828ba90b2 desiredImageState: Staged [...]How to reproduce
Create a cluster bink with a worker node and apply this yaml: