Closed rajgani closed 3 weeks ago
This issue is currently awaiting triage.
If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
@rajgani I think this was never implemented with this annotation name. It only shows up in the PR description there.
In general I would also recommend checking our current API vs old PRs for things that were added 5 years ago in our v1alpha1 API.
Anyway, this is how it should work today: (from our v1beta1 API)
/close
Please let me know if it also doesn't work with the correct annotation.
@sbueringer: Closing this issue.
I have a Cluster created with ByoH Provider and have the Worker node pool deployed as a machine deployment. I are trying to scale down a specific node from the worker node pool, I have tried by annotating
machineset.clusters.k8s.io/delete-me=yes
specific machine (as per the PR below) which has to be deleted, but its still picking the Random node when scaling down the Machine Deployment.https://github.com/kubernetes-sigs/cluster-api/pull/726