Init containers in GA - generated code

This commit is contained in:
Dominika Hodovska
2017-02-03 01:08:25 +01:00
parent 6c0191b31d
commit adf7cf1934
22 changed files with 1762 additions and 1236 deletions

View File

@@ -2496,6 +2496,21 @@ message PodSpec {
// +optional
repeated Volume volumes = 1;
// List of initialization containers belonging to the pod.
// Init containers are executed in order prior to containers being started. If any
// init container fails, the pod is considered to have failed and is handled according
// to its restartPolicy. The name for an init container or normal container must be
// unique among all containers.
// Init containers may not have Lifecycle actions, Readiness probes, or Liveness probes.
// The resourceRequirements of an init container are taken into account during scheduling
// by finding the highest request/limit for each resource type, and then using the max of
// of that value or the sum of the normal containers. Limits are applied to init containers
// in a similar fashion.
// Init containers cannot currently be added or removed.
// Cannot be updated.
// More info: http://kubernetes.io/docs/user-guide/containers
repeated Container initContainers = 20;
// List of containers belonging to the pod.
// Containers cannot currently be added or removed.
// There must be at least one container in a Pod.
@@ -2642,6 +2657,12 @@ message PodStatus {
// +optional
optional k8s.io.apimachinery.pkg.apis.meta.v1.Time startTime = 7;
// The list has one entry per init container in the manifest. The most recent successful
// init container will have ready = true, the most recently started container will have
// startTime set.
// More info: http://kubernetes.io/docs/user-guide/pod-states#container-statuses
repeated ContainerStatus initContainerStatuses = 10;
// The list has one entry per container in the manifest. Each entry is currently the output
// of `docker inspect`.
// More info: http://kubernetes.io/docs/user-guide/pod-states#container-statuses