Add init container documentation #679
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smarterclayton
force-pushed
the
initcontainer
branch
2 times, most recently
from
c822d88 to
47d7b09
Compare
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this pull request
Jun 18, 2016
Automatic merge from submit-queue Proposal for implementing init containers Addresses #1589. Implemented in #23567. Docs in kubernetes/website#679 ```release-note Init containers enable pod authors to perform tasks before their normal containers start. Each init container is started in order, and failing containers will prevent the application from starting. ```
|
@smarterclayton do we expect the usage to change a lot come beta? |
|
Expect? No. Maybe some tweaks to which features are supported, and the fact that it would not be using annotations. |
|
@smarterclayton The annotations was mainly what I was asking about. |
|
Excellent work, thanks @smarterclayton ! And thanks for the tech review, @pwittrock :) |
|
|
||
| Kubernetes now includes an alpha feature known as **init containers**, which are one or more containers in a pod that get a chance to run and initialize shared volumes prior to the other application containers starting. An init container is exactly like a regular container, except that it always runs to completion and each init container must complete successfully before the next one is started. If the init container fails (exits with a non-zero exit code) on a `RestartNever` pod the pod will fail - otherwise it will be restarted until it succeeds or the user deletes the pod. | ||
|
|
||
| Since init containers are an alpha feature, they are specified by setting the `pod.alpha.kubernetes.io/init-containers` annotation on a pod (or replica set, deployment, daemon set, pet set, or job). The value of the annotation must be a string containing a JSON array of container definitions: |
There was a problem hiding this comment.
string containing a JSON array of container definitions
I don't suppose it also supports YAML?
mikutas
pushed a commit
to mikutas/k8s-website
that referenced
this pull request
Feb 24, 2021
In helm chart for v2.7.0 variable names changed form ```Namespace``` to ```namespace``` and ```InstallNamespace``` to ```installNamespace``` Signed-off-by: Aliaksei Burau <aliakseiburov@gmail.com>
Okabe-Junya
pushed a commit
to Okabe-Junya/website
that referenced
this pull request
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves kubernetes/kubernetes#1589