Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle CAPI's block-move annotation #3839

Closed
Tracked by #3402
nojnhuh opened this issue Aug 14, 2023 · 0 comments · Fixed by #4213
Closed
Tracked by #3402

Handle CAPI's block-move annotation #3839

nojnhuh opened this issue Aug 14, 2023 · 0 comments · Fixed by #4213
Assignees
@nojnhuh
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@nojnhuh
Copy link
Contributor

nojnhuh commented Aug 14, 2023

/kind feature

Describe the solution you'd like
Once kubernetes-sigs/cluster-api#8690 merges (and lands in a released version that CAPZ pulls in), CAPZ should take advantage of that block-move annotation added by the PR to ensure ASO resources get fully paused before a cluster is moved.

Anything else you would like to add:
See also:
#3525
#3795

Environment:

  • cluster-api-provider-azure version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

/assign
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nojnhuh nojnhuh

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
CAPZ Planning
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

handle clusterctl block-move annotation nojnhuh/cluster-api-provider-azure
2 participants
@nojnhuh @k8s-ci-robot