Feature state: 1.0.0
A Pod can have multiple containers running apps within it.
Pods are designed to support multiple cooperating processes (as containers) that form a cohesive unit of service. The containers in a Pod are automatically co-located and co-scheduled on the same physical or virtual machine in the cluster. The containers can share resources and dependencies, communicate with one another, and coordinate when and how they are terminated.
additionalContainers value in Kubedeploy allow for defining one or more additionalContainers that will run alongside main application container.
By default, Kubedeploy does not specify any
additionalContainers values in Kubedeploy (click on the plus sign for more info):
- Define if initContainers are enabled.
- initContainers image pull policy
(optional) Define initContainers global resource requests and limits. Will be applied to all initContainers if more specific (per container) resource requests and limits are not defined.
(list) Sequential list of initContainers
- (required) Define initContainer name
- (required) Define initContainer repository
- (optional) Define initContainer image tag, defaults to
- (optional) Define custom command for initContainer
- (optional) Define custom arguments for initContainer
(optional) Define additionalContainer exposed ports (see: containerPort)
(optional) Enable custom healthcheck probes for additionalContainer
- (optional) Define custom resources for this specific additionalContainer
Additional containers can be used to augment application with additional functionality, for example defining extra container metric exporter, or using reverse authenticaton proxy.
additionalContainers will automatically inherit all the environment values set in
envFrom and volume mounts defined in
extraVoumeMounts just as the main container would.
Define additionalContainers that exports metrics