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

Index pods by node name for the daemon set controller #38868

Closed
0xmichalis opened this issue Dec 16, 2016 · 1 comment
Closed

Index pods by node name for the daemon set controller #38868

0xmichalis opened this issue Dec 16, 2016 · 1 comment
Labels
area/workload-api/daemonset lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/apps Categorizes an issue or PR as relevant to SIG Apps.

Comments

@0xmichalis
Copy link
Contributor

0xmichalis commented Dec 16, 2016

The daemonset controller fetches all pods in the system twice for every daemon set and node update in nodeShouldRunDaemonPod. We may want to add a NodeNameIndex in the pod cache and index pods by node, then use the index in the controller.

@kubernetes/sig-apps-misc @kubernetes/sig-node-misc

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/workload-api/daemonset lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/apps Categorizes an issue or PR as relevant to SIG Apps.
Projects
None yet
Development

No branches or pull requests

4 participants