-
Notifications
You must be signed in to change notification settings - Fork 158
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
Cross deletion of cluster tags in vSphere #13163
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/assign @ahmedwaleedmalik |
/milestone KKP 2.26 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
kubermatic-bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jul 24, 2024
/remove-lifecycle stale |
kubermatic-bot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Jul 26, 2024
/milestone clear |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Currently, the logic to clean up "tags" for clusters is the following:
This is highly problematic as we end up removing tags that are completely unrelated to this cluster. There should be no interference with unrelated/unlinked tags whatsoever.
How to reproduce the issue?
Create two clusters with tags A, B, and C,D, respectively against the same tag category. Don't assign those tags to machines or any other resources. C,D will be removed when first cluster is reconciled and A,B when the second cluster is reconciled.
How is your environment configured?
Additional information
The solution needs to be backported as well.
The text was updated successfully, but these errors were encountered: