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

Exit containers rather than sleep #11

Open
AverageMarcus opened this issue Oct 1, 2020 · 2 comments
Open

Exit containers rather than sleep #11

AverageMarcus opened this issue Oct 1, 2020 · 2 comments

Comments

@AverageMarcus
Copy link
Owner

As the DaemonSet is recreated on any change to needed images we have no need to keep the pods running on each node. Instead we should be able to exit each container with a 0 exit code and set the restart policy to only restart on failure.

@AverageMarcus
Copy link
Owner Author

It looks like this may not be possible with a Daemonset. Maybe It's worth looking in to creating a job that runs on all nodes?

@hholst80
Copy link

Why is the Daemonset recreated? Would it not be possible to have it change only if there is an actual change to the Daemonset itself rather than on a derived / dependent resource like a Deployment? If some kind of workload orchestration is required, maybe it would be a reasonable solution to have the Daemonset spawn up jobs that does the actual pull?

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

No branches or pull requests

2 participants