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.

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

Open
ahmedwaleedmalik opened this issue Mar 8, 2024 · 5 comments
Open

Cross deletion of cluster tags in vSphere #13163

ahmedwaleedmalik opened this issue Mar 8, 2024 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@ahmedwaleedmalik
Copy link
Member

What happened?

Currently, the logic to clean up "tags" for clusters is the following:

  • While reconciling a cluster check if tags exist
  • If they exist, fetch all tags against the tag category
  • Skip tags configured for that cluster and delete all the other tags that are not associated with any entity(other vSphere resources)

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?

  • KKP version: 2.23
  • Shared or separate master/seed clusters?:

Additional information

The solution needs to be backported as well.

@ahmedwaleedmalik ahmedwaleedmalik added the kind/bug Categorizes issue or PR as related to a bug. label Mar 8, 2024
@ahmedwaleedmalik
Copy link
Member Author

/assign @ahmedwaleedmalik

@ahmedwaleedmalik
Copy link
Member Author

/milestone KKP 2.26

@kubermatic-bot kubermatic-bot added this to the KKP 2.26 milestone Apr 24, 2024
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot 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
@steled
Copy link
Contributor

steled commented Jul 26, 2024

/remove-lifecycle stale

@kubermatic-bot 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
@csengerszabo
Copy link
Contributor

/milestone clear

@kubermatic-bot kubermatic-bot removed this from the KKP 2.26 milestone Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants