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

Sub cluster initiated multiple controllers for processing the same resource #801

Closed
zhenkuang opened this issue Apr 24, 2024 · 0 comments · Fixed by #802
Closed

Sub cluster initiated multiple controllers for processing the same resource #801

zhenkuang opened this issue Apr 24, 2024 · 0 comments · Fixed by #802
Labels
kind/bug Something isn't working

Comments

@zhenkuang
Copy link
Contributor

zhenkuang commented Apr 24, 2024

What happened:

When the clusternet agent is started, the controller will be started according to the delivered resource type to synchronize the resource status, but we find that the sub cluster occasionally initiated multiple controllers for processing the same resource .
企业微信截图_f79fb96f-0a55-4ef7-97ca-f30131019622
企业微信截图_007c1526-d98b-410a-b2eb-9ef58dc9989f

https://github.com/clusternet/clusternet/blob/main/pkg/agent/deployer/generic/generic.go#L178-L182

What you expected to happen:

The agent should only start one controller to handle one resource

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Clusternet version:
    • Clusternet-agent version (user clusternet-agent --version=json):
    • Clusternet-hub version (user clusternet-hub --version=json):
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:
@zhenkuang zhenkuang added the kind/bug Something isn't working label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant