pub struct PodSpec {Show 26 fields
pub active_deadline_seconds: Option<i64>,
pub affinity: Option<Affinity>,
pub automount_service_account_token: Option<bool>,
pub containers: Vec<Container>,
pub dns_config: Option<PodDNSConfig>,
pub dns_policy: Option<String>,
pub host_aliases: Option<Vec<HostAlias>>,
pub host_ipc: Option<bool>,
pub host_network: Option<bool>,
pub host_pid: Option<bool>,
pub hostname: Option<String>,
pub image_pull_secrets: Option<Vec<LocalObjectReference>>,
pub init_containers: Option<Vec<Container>>,
pub node_name: Option<String>,
pub node_selector: Option<BTreeMap<String, String>>,
pub priority: Option<i32>,
pub priority_class_name: Option<String>,
pub restart_policy: Option<String>,
pub scheduler_name: Option<String>,
pub security_context: Option<PodSecurityContext>,
pub service_account: Option<String>,
pub service_account_name: Option<String>,
pub subdomain: Option<String>,
pub termination_grace_period_seconds: Option<i64>,
pub tolerations: Option<Vec<Toleration>>,
pub volumes: Option<Vec<Volume>>,
}Expand description
PodSpec is a description of a pod.
Fields§
§active_deadline_seconds: Option<i64>Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.
affinity: Option<Affinity>If specified, the pod’s scheduling constraints
automount_service_account_token: Option<bool>AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.
containers: Vec<Container>List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.
dns_config: Option<PodDNSConfig>Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy. This is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it.
dns_policy: Option<String>Set DNS policy for the pod. Defaults to “ClusterFirst”. Valid values are ‘ClusterFirstWithHostNet’, ‘ClusterFirst’, ‘Default’ or ‘None’. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to ‘ClusterFirstWithHostNet’. Note that ‘None’ policy is an alpha feature introduced in v1.9 and CustomPodDNS feature gate must be enabled to use it.
host_aliases: Option<Vec<HostAlias>>HostAliases is an optional list of hosts and IPs that will be injected into the pod’s hosts file if specified. This is only valid for non-hostNetwork pods.
host_ipc: Option<bool>Use the host’s ipc namespace. Optional: Default to false.
host_network: Option<bool>Host networking requested for this pod. Use the host’s network namespace. If this option is set, the ports that will be used must be specified. Default to false.
host_pid: Option<bool>Use the host’s pid namespace. Optional: Default to false.
hostname: Option<String>Specifies the hostname of the Pod If not specified, the pod’s hostname will be set to a system-defined value.
image_pull_secrets: Option<Vec<LocalObjectReference>>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: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod
init_containers: Option<Vec<Container>>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: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
node_name: Option<String>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.
node_selector: Option<BTreeMap<String, String>>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node’s labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
priority: Option<i32>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.
priority_class_name: Option<String>If specified, indicates the pod’s priority. “SYSTEM” is a special keyword which indicates the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.
restart_policy: Option<String>Restart policy for all containers within the pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
scheduler_name: Option<String>If specified, the pod will be dispatched by specified scheduler. If not specified, the pod will be dispatched by default scheduler.
security_context: Option<PodSecurityContext>SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty. See type description for default values of each field.
service_account: Option<String>DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.
service_account_name: Option<String>ServiceAccountName is the name of the ServiceAccount to use to run this pod. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
subdomain: Option<String>If specified, the fully qualified Pod hostname will be “
termination_grace_period_seconds: Option<i64>Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.
tolerations: Option<Vec<Toleration>>If specified, the pod’s tolerations.
volumes: Option<Vec<Volume>>List of volumes that can be mounted by containers belonging to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes