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 not Daemon set? #199

Open
McAndersDK opened this issue Jan 19, 2023 · 1 comment
Open

Why not Daemon set? #199

McAndersDK opened this issue Jan 19, 2023 · 1 comment
Labels
question Further information is requested

Comments

@McAndersDK
Copy link

Hey all,

Any reason for not using a daemon set with the cri-client image?
and have them work and react to a aggregated configmap with all the image caches?
This way we will eliminate alle jobs, CNI work, kubelet work, kubeproxy work, API work.
We will make sure that we just have an ongoing container on each worker node that will interact with the CRI.
We would also be able to batch process all images updates inside one container pr worker node.

is there something I dont see?

@senthilrch senthilrch added the question Further information is requested label Mar 5, 2023
@gaocegege
Copy link
Contributor

Same question here. daemonset looks great in this use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants