How to categorize this issue?
/area ops-productivity
/kind bug
What happened:
❯ k -n ... get machine <machine> -o yaml | yq .status
currentStatus:
lastUpdateTime: "2026-01-16T10:04:42Z"
phase: Pending
timeoutActive: true
lastOperation:
description: Creating machine on cloud provider
lastUpdateTime: "2026-01-16T10:04:42Z"
state: Processing
type: Create
❯ aws ec2 describe-instances ... --query 'Reservations[].Instances[].[Tags[?Key==`Name`] | [0].Value, State.Name]'
[
[
"<machine>",
"running"
]
]
❯ k get nodes
(empty)
What you expected to happen:
The above example shows a successfully created machine on the cloud provider but a failure in kubelet registering the node. In this case a more appropriate description would be Waiting for kubelet to create node object.
This message will improve debugging failing shoot clusters as it is much more accurate
Environment:
- Kubernetes version (use
kubectl version):
- Cloud provider or hardware configuration:
- Others:
How to categorize this issue?
/area ops-productivity
/kind bug
What happened:
What you expected to happen:
The above example shows a successfully created machine on the cloud provider but a failure in kubelet registering the node. In this case a more appropriate description would be
Waiting for kubelet to create node object.This message will improve debugging failing shoot clusters as it is much more accurate
Environment:
kubectl version):