pub struct Container {Show 24 fields
pub args: Option<Vec<String>>,
pub command: Option<Vec<String>>,
pub env: Option<Vec<EnvVar>>,
pub env_from: Option<Vec<EnvFromSource>>,
pub image: Option<String>,
pub image_pull_policy: Option<String>,
pub lifecycle: Option<Lifecycle>,
pub liveness_probe: Option<Probe>,
pub name: String,
pub ports: Option<Vec<ContainerPort>>,
pub readiness_probe: Option<Probe>,
pub resize_policy: Option<Vec<ContainerResizePolicy>>,
pub resources: Option<ResourceRequirements>,
pub restart_policy: Option<String>,
pub security_context: Option<SecurityContext>,
pub startup_probe: Option<Probe>,
pub stdin: Option<bool>,
pub stdin_once: Option<bool>,
pub termination_message_path: Option<String>,
pub termination_message_policy: Option<String>,
pub tty: Option<bool>,
pub volume_devices: Option<Vec<VolumeDevice>>,
pub volume_mounts: Option<Vec<VolumeMount>>,
pub working_dir: Option<String>,
}Expand description
A single application container that you want to run within a pod.
Fields§
§args: Option<Vec<String>>Arguments to the entrypoint. The container image’s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell
command: Option<Vec<String>>Entrypoint array. Not executed within a shell. The container image’s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell
env: Option<Vec<EnvVar>>List of environment variables to set in the container. Cannot be updated.
env_from: Option<Vec<EnvFromSource>>List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.
image: Option<String>Container image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.
image_pull_policy: Option<String>Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images
lifecycle: Option<Lifecycle>Actions that the management system should take in response to container lifecycle events. Cannot be updated.
liveness_probe: Option<Probe>Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
name: StringName of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.
ports: Option<Vec<ContainerPort>>List of ports to expose from the container. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default “0.0.0.0” address inside a container will be accessible from the network. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. Cannot be updated.
readiness_probe: Option<Probe>Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
resize_policy: Option<Vec<ContainerResizePolicy>>Resources resize policy for the container.
resources: Option<ResourceRequirements>Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
restart_policy: Option<String>RestartPolicy defines the restart behavior of individual containers in a pod. This field may only be set for init containers, and the only allowed value is “Always”. For non-init containers or when this field is not specified, the restart behavior is defined by the Pod’s restart policy and the container type. Setting the RestartPolicy as “Always” for the init container will have the following effect: this init container will be continually restarted on exit until all regular containers have terminated. Once all regular containers have completed, all init containers with restartPolicy “Always” will be shut down. This lifecycle differs from normal init containers and is often referred to as a “sidecar” container. Although this init container still starts in the init container sequence, it does not wait for the container to complete before proceeding to the next init container. Instead, the next init container starts immediately after this init container is started, or after any startupProbe has successfully completed.
security_context: Option<SecurityContext>SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
startup_probe: Option<Probe>StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod’s lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
stdin: Option<bool>Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.
stdin_once: Option<bool>Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
termination_message_path: Option<String>Optional: Path at which the file to which the container’s termination message will be written is mounted into the container’s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.
termination_message_policy: Option<String>Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.
tty: Option<bool>Whether this container should allocate a TTY for itself, also requires ‘stdin’ to be true. Default is false.
volume_devices: Option<Vec<VolumeDevice>>volumeDevices is the list of block devices to be used by the container.
volume_mounts: Option<Vec<VolumeMount>>Pod volumes to mount into the container’s filesystem. Cannot be updated.
working_dir: Option<String>Container’s working directory. If not specified, the container runtime’s default will be used, which might be configured in the container image. Cannot be updated.
Trait Implementations§
Source§impl DeepMerge for Container
impl DeepMerge for Container
Source§fn merge_from(&mut self, other: Self)
fn merge_from(&mut self, other: Self)
other into self.