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

Application/resource is taking too much time to remove from cluster, when cluster groups are changed in GitRepo #3091

Open
1 task done
sbulage opened this issue Nov 22, 2024 · 1 comment
Labels

Comments

@sbulage
Copy link
Contributor

sbulage commented Nov 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

After changing cluster groups using (containing different set of clusters) in GitRepo, taking too much time to remove resource from cluster. I observed it took more than 2-3 mins.

Expected Behavior

Application or resource should be removed within few seconds and should not take much time to remove it.

Steps To Reproduce

  1. Add same labels to the cluster-A and Cluster-B
  2. Create a cluster group of cluster-A and cluster-B using same label.
  3. Create a GitRepo and in Deploy To section select cluster group name.
  4. Wait for resources created on both clusters.
  5. For Third cluster-C, add new label to it.
  6. Create another cluster group of third cluster-C using new label (added on cluster-C)
  7. Update GitRepo with newly created cluster group.
  8. Wait for the application to be create on third cluster-C.

Environment

- Architecture:
- Fleet Version:0.11.1
- Cluster:
  - Provider:k3s
  - Options:
  - Kubernetes Version: v1.28.8+k3s1

Logs

No response

Anything else?

Video Showing Application stays after changing Cluster groups to GitRepo

(https://github.com/user-attachments/assets/14168b87-915b-4416-8bd0-27d4fdbcbcc1)

@sbulage sbulage added this to Fleet Nov 22, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Fleet Nov 22, 2024
@manno
Copy link
Member

manno commented Dec 11, 2024

Does this happen if you only create cluster group A and not a second one B targeting the same label?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants