-
Notifications
You must be signed in to change notification settings - Fork 108
🐛 Do not leave resources on the system after removing a provider #179
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.
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
Conversation
Client proxy defines among which types we will search for objects with the desired labels. Currently this list is not full and we skip some types, like ClusterRole or ClusterRole bindings. It leads to the fact that objects of these types stay in the system when their provider is deleted. This PR updates the list of resource types we need to scan.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-demicev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 8354a3e9439012248072fa8949a83f04621c5dd1
|
/retest |
>_< |
/retest |
1 similar comment
/retest |
What this PR does / why we need it:
Client proxy defines among which types we will search for objects we need to delete. Currently this list is not full and we skip some types, like ClusterRole or ClusterRole bindings. It leads to the fact that objects of these types stay in the system when their provider is deleted.
This PR updates the list of resource types we need to scan.
Note: for now, we will not delete CRDs and namespaces as it's the default behavior of clusterctl. But we still want to scan them because it will make it easier to manage their removal in the future: https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/internal/controller/phases.go#L413-L417
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #