Update CAPI support to 1.9 #525
Assignees
Labels
area/api
Indicates an issue or PR relates to the APIs
area/dependency
Issues or PRs related to dependency changes
Milestone
Comments
Danil-Grigorev
added
area/api
Danil-Grigorev
moved this to CAPI Backlog
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
|
Issues can be reproduced on #526 which only updates CAPI to 1.9 without changing the code. It appears kubernetes-sigs/cluster-api#11457 has a check which resolves the problem, but it applies only for kubeadm CP provider. |
|
After some investigation opened kubernetes-sigs/cluster-api#11591 and a fix kubernetes-sigs/cluster-api#11590 which unblocked machine deletion after update |
Danil-Grigorev
moved this from CAPI Backlog
to In Progress (8 max)
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Danil-Grigorev
moved this from In Progress (8 max)
to Blocked
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
|
From the discussion it seems there is https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240916-improve-status-in-CAPI-resources.md#machine-newconditions proposes removal of existing conditions in the future, which acts as a way to ensure draining success and volume detachment success does terminate further attempts. |
github-project-automation
bot
moved this from Blocked
to Done
in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an epic for 1.9 update, and changes required to facilitate that.
The text was updated successfully, but these errors were encountered: