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

Why are there three klusterlet pods in a managed cluster?(problem) #479

Open
Willy1999927 opened this issue May 28, 2024 · 3 comments
Open
Labels

Comments

@Willy1999927
Copy link

Willy1999927 commented May 28, 2024

In the cluster I have with one master and two workers, why are there three klusterlet pods used to pull the configuration and execute it? Do you have a complete architecture diagram?

xxx@xxx:/home/cdlab# kubectl get pods -n open-cluster-management -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
klusterlet-67d4cdc69-5mms5 1/1 Running 16 (16h ago) 29d 10.244.43.1 worker1
klusterlet-67d4cdc69-bk49j 1/1 Running 4 (24h ago) 29d 10.244.43.2 wroker1
klusterlet-67d4cdc69-x75hk 1/1 Running 12 (16h ago) 29d 10.244.70.132 worker2

@qiujian16
Copy link
Member

The number or replica is decided here https://github.com/open-cluster-management-io/ocm/blob/main/pkg/operator/helpers/helpers.go#L435. The is mainly for the HA case, and ensure the agent keeps on running during rolling upgrade.

@Willy1999927
Copy link
Author

OK,thanks for your reply

Copy link

github-actions bot commented Oct 2, 2024

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants