Interface DeploymentProps

Indicates whether a service account token should be automatically mounted.

List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod.

You can add additionnal containers using podSpec.addContainer()

DNS settings for the pod.

A secret containing docker credentials for authenticating to a registry.

HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod's hosts file.

Host network for the pod.

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, Liveness probes, or Startup 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 ,removed or updated.

Isolates the pod. This will prevent any ingress or egress connections to / from this pod. You can however allow explicit connections post instantiation by using the .connections property.

Metadata that all persisted resources must have, which includes all objects users must create.

The pod metadata of this workload.

Restart policy for all containers within the pod.

SecurityContext holds pod-level security attributes and common container settings.

Automatically allocates a pod label selector for this workload and add it to the pod metadata. This ensures this workload manages pods created by its pod template.

A service account provides an identity for processes that run in a Pod.

When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default).

When process namespace sharing is enabled, processes in a container are visible to all other containers in the same pod.

Automatically spread pods across hostname and zones.

Grace period until the pod is terminated

List of volumes that can be mounted by containers belonging to the pod.

You can also add volumes later using podSpec.addVolume()