Files
Aleksei Sviridkin 01a071a720 test(e2e): read MachineDeployment readiness through the v1beta1 API
The Kubernetes suite waited on status.v1beta2.readyReplicas through a
bare "machinedeployment" resource name. That name resolves to the
version the cluster prefers: v1beta1 under Cluster API v1.10, v1beta2
from v1.11. In v1beta2 the counter is status.readyReplicas and
status.v1beta2 does not exist, so after a Cluster API upgrade the wait
would run out its ten minutes and fail.

The wait now names the v1beta1 resource, which carries
status.v1beta2.readyReplicas on both sides of the upgrade and is
served until Cluster API v1.16.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-10-12 23:36:49 +03:00
..