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.

Sign up for GitHub

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

Jump to bottom

Support init containers per deployment #36477

Closed
F21 opened this issue Nov 9, 2016 · 2 comments
Closed

Support init containers per deployment #36477

F21 opened this issue Nov 9, 2016 · 2 comments
Labels
area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@F21
Copy link

F21 commented Nov 9, 2016

The current behavior of init containers is to run a set of init containers for every pod.

It would be nice if the behavior could be extended so that we can define a set of init containers for a deployment. This would be extremely useful if we have an app that talks to a database and would need to run database migrations or perform some action or task exclusively for the whole deployment during startup. We can then run these tasks in an init container, but only in 1 container per deployment.
@k8s-github-robot k8s-github-robot added area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. labels Nov 9, 2016
@0xmichalis
Copy link
Contributor

@kubernetes/deployment @smarterclayton

@0xmichalis
Copy link
Contributor

Closing as a duplicate of #14512

@escattone escattone mentioned this issue Aug 30, 2017
Closed
@Jefferson-Faseler Jefferson-Faseler mentioned this issue Feb 27, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@F21 @0xmichalis @k8s-github-robot