Skip to content

Commit

Permalink
[ALIEN-3564] initContainer Tosca model is not correct
Browse files Browse the repository at this point in the history
  • Loading branch information
SebastienLaurent committed Dec 3, 2020
1 parent 34709fd commit 6aca1e1
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion src/main/resources/csar/tosca.yml
Original file line number Diff line number Diff line change
Expand Up @@ -435,8 +435,10 @@ data_types:
description: |
ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: http://kubernetes.io/docs/user-guide/images#specifying-imagepullsecrets-on-a-pod
initContainers:
type: org.alien4cloud.kubernetes.api.datatypes.ContainerSpec
type: list
required: false
entry_schema:
type: org.alien4cloud.kubernetes.api.datatypes.ContainerSpec
description: |
array 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
nodeName:
Expand Down

0 comments on commit 6aca1e1

Please sign in to comment.