--- title: "returns detailed information about Pod" method: GET path: "/api/v1/pod/{namespace}/{pod}" --- # returns detailed information about Pod `GET /api/v1/pod/{namespace}/{pod}` ## Path parameters - `namespace` string, required - `pod` string, required ## Query parameters - `filterBy` string - `sortBy` string - `itemsPerPage` string - `page` string - `metricNames` string - `aggregations` string ## Response `200` OK - PodPodDetail - `conditions` CommonCondition[], required - `lastProbeTime` V1Time, required - `Time` string, date-time, required - `lastTransitionTime` V1Time, required - `Time` string, date-time, required - `message` string, required - `reason` string, required - `status` string, required - `type` string, required - `containers` PodContainer[], required - `args` string[], required - `commands` string[], required - `env` PodEnvVar[], required - `name` string, required - `value` string, required - `valueFrom` V1EnvVarSource, required — EnvVarSource represents a source for the value of an EnvVar. - `configMapKeyRef` V1ConfigMapKeySelector — Selects a key from a ConfigMap. - `key` string, required — The key to select. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — Specify whether the ConfigMap or its key must be defined - `fieldRef` V1ObjectFieldSelector — ObjectFieldSelector selects an APIVersioned field of an object. - `apiVersion` string — Version of the schema the FieldPath is written in terms of, defaults to "v1". - `fieldPath` string, required — Path of the field to select in the specified API version. - `resourceFieldRef` V1ResourceFieldSelector — ResourceFieldSelector represents container resources (cpu, memory) and their output format - `containerName` string — Container name: required for volumes, optional for env vars - `divisor` ResourceQuantity - `Format` string, required - `d` ResourceInfDecAmount, required - … - `i` ResourceInt64Amount, required - … - `s` string, required - `resource` string, required — Required: resource to select - `secretKeyRef` V1SecretKeySelector — SecretKeySelector selects a key of a Secret. - `key` string, required — The key of the secret to select from. Must be a valid secret key. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — Specify whether the Secret or its key must be defined - `image` string, required - `livenessProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `name` string, required - `readinessProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `resources` V1ResourceRequirements — ResourceRequirements describes the compute resource requirements. - `claims` V1ResourceClaim[] — Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers. - `name` string, required — Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. - `limits` object — Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `requests` object — Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `securityContext` V1SecurityContext, required — SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext. When both are set, the values in SecurityContext take precedence. - `allowPrivilegeEscalation` boolean — AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN Note that this field cannot be set when spec.os.name is windows. - `appArmorProfile` V1AppArmorProfile — AppArmorProfile defines a pod or container's AppArmor settings. - `localhostProfile` string — localhostProfile indicates a profile loaded on the node that should be used. The profile must be preconfigured on the node to work. Must match the loaded name of the profile. Must be set if and only if type is "Localhost". - `type` string, required — type indicates which kind of AppArmor profile will be applied. Valid options are: Localhost - a profile pre-loaded on the node. RuntimeDefault - the container runtime's default profile. Unconfined - no AppArmor enforcement. - `capabilities` V1Capabilities — Adds and removes POSIX capabilities from running containers. - `add` string[] — Added capabilities - `drop` string[] — Removed capabilities - `privileged` boolean — Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows. - `procMount` string — procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows. - `readOnlyRootFilesystem` boolean — Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows. - `runAsGroup` integer — The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. - `runAsNonRoot` boolean — Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `runAsUser` integer — The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. - `seLinuxOptions` V1SELinuxOptions — SELinuxOptions are the labels to be applied to the container - `level` string — Level is SELinux level label that applies to the container. - `role` string — Role is a SELinux role label that applies to the container. - `type` string — Type is a SELinux type label that applies to the container. - `user` string — User is a SELinux user label that applies to the container. - `seccompProfile` V1SeccompProfile — SeccompProfile defines a pod/container's seccomp profile settings. Only one profile source may be set. - `localhostProfile` string — localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type. - `type` string, required — type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied. - `windowsOptions` V1WindowsSecurityContextOptions — WindowsSecurityContextOptions contain Windows-specific options and credentials. - `gmsaCredentialSpec` string — GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. - `gmsaCredentialSpecName` string — GMSACredentialSpecName is the name of the GMSA credential spec to use. - `hostProcess` boolean — HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true. - `runAsUserName` string — The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `startupProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `state` string, required - `status` V1ContainerStatus, required — ContainerStatus contains details for the current status of this container. - `allocatedResources` object — AllocatedResources represents the compute resources allocated for this container by the node. Kubelet sets this value to Container.Resources.Requests upon successful pod admission and after successfully admitting desired pod resize. - `containerID` string — ContainerID is the ID of the container in the format '://'. Where type is a container runtime identifier, returned from Version call of CRI API (for example "containerd"). - `image` string, required — Image is the name of container image that the container is running. The container image may not match the image used in the PodSpec, as it may have been resolved by the runtime. More info: https://kubernetes.io/docs/concepts/containers/images. - `imageID` string, required — ImageID is the image ID of the container's image. The image ID may not match the image ID of the image used in the PodSpec, as it may have been resolved by the runtime. - `lastState` V1ContainerState — ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting. - `running` V1ContainerStateRunning — ContainerStateRunning is a running state of a container. - `startedAt` V1Time - `Time` string, date-time, required - `terminated` V1ContainerStateTerminated — ContainerStateTerminated is a terminated state of a container. - `containerID` string — Container's ID in the format '://' - `exitCode` integer, required — Exit status from the last termination of the container - `finishedAt` V1Time - `Time` string, date-time, required - `message` string — Message regarding the last termination of the container - `reason` string — (brief) reason from the last termination of the container - `signal` integer — Signal from the last termination of the container - `startedAt` V1Time - `Time` string, date-time, required - `waiting` V1ContainerStateWaiting — ContainerStateWaiting is a waiting state of a container. - `message` string — Message regarding why the container is not yet running. - `reason` string — (brief) reason the container is not yet running. - `name` string, required — Name is a DNS_LABEL representing the unique name of the container. Each container in a pod must have a unique name across all container types. Cannot be updated. - `ready` boolean, required — Ready specifies whether the container is currently passing its readiness check. The value will change as readiness probes keep executing. If no readiness probes are specified, this field defaults to true once the container is fully started (see Started field). The value is typically used to determine whether a container is ready to accept traffic. - `resources` V1ResourceRequirements — ResourceRequirements describes the compute resource requirements. - `claims` V1ResourceClaim[] — Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers. - `name` string, required — Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. - `limits` object — Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `requests` object — Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `restartCount` integer, required — RestartCount holds the number of times the container has been restarted. Kubelet makes an effort to always increment the value, but there are cases when the state may be lost due to node restarts and then the value may be reset to 0. The value is never negative. - `started` boolean — Started indicates whether the container has finished its postStart lifecycle hook and passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle hook. The null value must be treated the same as false. - `state` V1ContainerState — ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting. - `running` V1ContainerStateRunning — ContainerStateRunning is a running state of a container. - `startedAt` V1Time - `Time` string, date-time, required - `terminated` V1ContainerStateTerminated — ContainerStateTerminated is a terminated state of a container. - `containerID` string — Container's ID in the format '://' - `exitCode` integer, required — Exit status from the last termination of the container - `finishedAt` V1Time - `Time` string, date-time, required - `message` string — Message regarding the last termination of the container - `reason` string — (brief) reason from the last termination of the container - `signal` integer — Signal from the last termination of the container - `startedAt` V1Time - `Time` string, date-time, required - `waiting` V1ContainerStateWaiting — ContainerStateWaiting is a waiting state of a container. - `message` string — Message regarding why the container is not yet running. - `reason` string — (brief) reason the container is not yet running. - `volumeMounts` V1VolumeMountStatus[] — Status of volume mounts. - `mountPath` string, required — MountPath corresponds to the original VolumeMount. - `name` string, required — Name corresponds to the name of the original VolumeMount. - `readOnly` boolean — ReadOnly corresponds to the original VolumeMount. - `recursiveReadOnly` string — RecursiveReadOnly must be set to Disabled, Enabled, or unspecified (for non-readonly mounts). An IfPossible value in the original VolumeMount must be translated to Disabled or Enabled, depending on the mount result. - `volumeMounts` PodVolumeMount[], required - `mountPath` string, required - `name` string, required - `readOnly` boolean, required - `subPath` string, required - `volume` V1Volume, required — Volume represents a named volume in a pod that may be accessed by any container in the pod. - `awsElasticBlockStore` V1AWSElasticBlockStoreVolumeSource — Represents a Persistent Disk resource in AWS. An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `partition` integer — partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). - `readOnly` boolean — readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `volumeID` string, required — volumeID is unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `azureDisk` V1AzureDiskVolumeSource — AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod. - `cachingMode` string — cachingMode is the Host Caching mode: None, Read Only, Read Write. - `diskName` string, required — diskName is the Name of the data disk in the blob storage - `diskURI` string, required — diskURI is the URI of data disk in the blob storage - `fsType` string — fsType is Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `kind` string — kind expected values are Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared - `readOnly` boolean — readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `azureFile` V1AzureFileVolumeSource — AzureFile represents an Azure File Service mount on the host and bind mount to the pod. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretName` string, required — secretName is the name of secret that contains Azure Storage Account Name and Key - `shareName` string, required — shareName is the azure share Name - `cephfs` V1CephFSVolumeSource — Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling. - `monitors` string[], required — monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `path` string — path is Optional: Used as the mounted root, rather than the full Ceph tree, default is / - `readOnly` boolean — readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `secretFile` string — secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `user` string — user is optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `cinder` V1CinderVolumeSource — Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `volumeID` string, required — volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `configMap` V1ConfigMapVolumeSource — Adapts a ConfigMap into a volume. The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling. - `defaultMode` integer — defaultMode is optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1KeyToPath[] — items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. - `key` string, required — key is the key to project. - `mode` integer — mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — optional specify whether the ConfigMap or its keys must be defined - `csi` V1CSIVolumeSource — Represents a source location of a volume to mount, managed by an external CSI driver - `driver` string, required — driver is the name of the CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster. - `fsType` string — fsType to mount. Ex. "ext4", "xfs", "ntfs". If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply. - `nodePublishSecretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `readOnly` boolean — readOnly specifies a read-only configuration for the volume. Defaults to false (read/write). - `volumeAttributes` object — volumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver's documentation for supported values. - `downwardAPI` V1DownwardAPIVolumeSource — DownwardAPIVolumeSource represents a volume containing downward API info. Downward API volumes support ownership management and SELinux relabeling. - `defaultMode` integer — Optional: mode bits to use on created files by default. Must be a Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1DownwardAPIVolumeFile[] — Items is a list of downward API volume file - `fieldRef` V1ObjectFieldSelector — ObjectFieldSelector selects an APIVersioned field of an object. - … - `mode` integer — Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..' - `resourceFieldRef` V1ResourceFieldSelector — ResourceFieldSelector represents container resources (cpu, memory) and their output format - … - `emptyDir` V1EmptyDirVolumeSource — Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling. - `medium` string — medium represents what type of storage medium should back this directory. The default is "" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir - `sizeLimit` ResourceQuantity - `Format` string, required - `d` ResourceInfDecAmount, required - … - `i` ResourceInt64Amount, required - … - `s` string, required - `ephemeral` V1EphemeralVolumeSource — Represents an ephemeral volume that is handled by a normal storage driver. - `volumeClaimTemplate` V1PersistentVolumeClaimTemplate — PersistentVolumeClaimTemplate is used to produce PersistentVolumeClaim objects as part of an EphemeralVolumeSource. - `metadata` V1ObjectMeta — ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create. - … - `spec` V1PersistentVolumeClaimSpec, required — PersistentVolumeClaimSpec describes the common attributes of storage devices and allows a Source for provider-specific attributes - … - `fc` V1FCVolumeSource — Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `lun` integer — lun is Optional: FC target lun number - `readOnly` boolean — readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `targetWWNs` string[] — targetWWNs is Optional: FC target worldwide names (WWNs) - `wwids` string[] — wwids Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously. - `flexVolume` V1FlexVolumeSource — FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. - `driver` string, required — driver is the name of the driver to use for this volume. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script. - `options` object — options is Optional: this field holds extra command options if any. - `readOnly` boolean — readOnly is Optional: defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `flocker` V1FlockerVolumeSource — Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling. - `datasetName` string — datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker should be considered as deprecated - `datasetUUID` string — datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset - `gcePersistentDisk` V1GCEPersistentDiskVolumeSource — Represents a Persistent Disk resource in Google Compute Engine. A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling. - `fsType` string — fsType is filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `partition` integer — partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `pdName` string, required — pdName is unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `gitRepo` V1GitRepoVolumeSource — Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container. - `directory` string — directory is the target directory name. Must not contain or start with '..'. If '.' is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name. - `repository` string, required — repository is the URL - `revision` string — revision is the commit hash for the specified revision. - `glusterfs` V1GlusterfsVolumeSource — Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling. - `endpoints` string, required — endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `path` string, required — path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `readOnly` boolean — readOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `hostPath` V1HostPathVolumeSource — Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling. - `path` string, required — path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath - `type` string — type for HostPath Volume Defaults to "" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath - `iscsi` V1ISCSIVolumeSource — Represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling. - `chapAuthDiscovery` boolean — chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication - `chapAuthSession` boolean — chapAuthSession defines whether support iSCSI Session CHAP authentication - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi - `initiatorName` string — initiatorName is the custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface : will be created for the connection. - `iqn` string, required — iqn is the target iSCSI Qualified Name. - `iscsiInterface` string — iscsiInterface is the interface Name that uses an iSCSI transport. Defaults to 'default' (tcp). - `lun` integer, required — lun represents iSCSI Target Lun number. - `portals` string[] — portals is the iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `targetPortal` string, required — targetPortal is iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). - `name` string, required — name of the volume. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `nfs` V1NFSVolumeSource — Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling. - `path` string, required — path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `readOnly` boolean — readOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `server` string, required — server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `persistentVolumeClaim` V1PersistentVolumeClaimVolumeSource — PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system). - `claimName` string, required — claimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims - `readOnly` boolean — readOnly Will force the ReadOnly setting in VolumeMounts. Default false. - `photonPersistentDisk` V1PhotonPersistentDiskVolumeSource — Represents a Photon Controller persistent disk resource. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `pdID` string, required — pdID is the ID that identifies Photon Controller persistent disk - `portworxVolume` V1PortworxVolumeSource — PortworxVolumeSource represents a Portworx volume resource. - `fsType` string — fSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs". Implicitly inferred to be "ext4" if unspecified. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `volumeID` string, required — volumeID uniquely identifies a Portworx volume - `projected` V1ProjectedVolumeSource — Represents a projected volume source - `defaultMode` integer — defaultMode are the mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `sources` V1VolumeProjection[], required — sources is the list of volume projections - `clusterTrustBundle` V1ClusterTrustBundleProjection — ClusterTrustBundleProjection describes how to select a set of ClusterTrustBundle objects and project their contents into the pod filesystem. - … - `configMap` V1ConfigMapProjection — Adapts a ConfigMap into a projected volume. The contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode. - … - `downwardAPI` V1DownwardAPIProjection — Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode. - … - `secret` V1SecretProjection — Adapts a secret into a projected volume. The contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode. - … - `serviceAccountToken` V1ServiceAccountTokenProjection — ServiceAccountTokenProjection represents a projected service account token volume. This projection can be used to insert a service account token into the pods runtime filesystem for use against APIs (Kubernetes API Server or otherwise). - … - `quobyte` V1QuobyteVolumeSource — Represents a Quobyte mount that lasts the lifetime of a pod. Quobyte volumes do not support ownership management or SELinux relabeling. - `group` string — group to map volume access to Default is no group - `readOnly` boolean — readOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false. - `registry` string, required — registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes - `tenant` string — tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin - `user` string — user to map volume access to Defaults to serivceaccount user - `volume` string, required — volume is a string that references an already created Quobyte volume by name. - `rbd` V1RBDVolumeSource — Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd - `image` string, required — image is the rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `keyring` string — keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `monitors` string[], required — monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `pool` string — pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `user` string — user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `scaleIO` V1ScaleIOVolumeSource — ScaleIOVolumeSource represents a persistent ScaleIO volume - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Default is "xfs". - `gateway` string, required — gateway is the host address of the ScaleIO API Gateway. - `protectionDomain` string — protectionDomain is the name of the ScaleIO Protection Domain for the configured storage. - `readOnly` boolean — readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference, required — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `sslEnabled` boolean — sslEnabled Flag enable/disable SSL communication with Gateway, default false - `storageMode` string — storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned. - `storagePool` string — storagePool is the ScaleIO Storage Pool associated with the protection domain. - `system` string, required — system is the name of the storage system as configured in ScaleIO. - `volumeName` string — volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source. - `secret` V1SecretVolumeSource — Adapts a Secret into a volume. The contents of the target Secret's Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling. - `defaultMode` integer — defaultMode is Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1KeyToPath[] — items If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. - `key` string, required — key is the key to project. - `mode` integer — mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. - `optional` boolean — optional field specify whether the Secret or its keys must be defined - `secretName` string — secretName is the name of the secret in the pod's namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret - `storageos` V1StorageOSVolumeSource — Represents a StorageOS persistent volume resource. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `volumeName` string — volumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace. - `volumeNamespace` string — volumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod's namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to "default" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created. - `vsphereVolume` V1VsphereVirtualDiskVolumeSource — Represents a vSphere volume resource. - `fsType` string — fsType is filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `storagePolicyID` string — storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName. - `storagePolicyName` string — storagePolicyName is the storage Policy Based Management (SPBM) profile name. - `volumePath` string, required — volumePath is the path that identifies vSphere volume vmdk - `controller` ControllerResourceOwner - `containerImages` string[], required - `initContainerImages` string[], required - `objectMeta` TypesObjectMeta, required - `annotations` object - `creationTimestamp` V1Time - `Time` string, date-time, required - `labels` object - `name` string - `namespace` string - `uid` string - `pods` CommonPodInfo, required - `current` integer, required - `desired` integer - `failed` integer, required - `pending` integer, required - `running` integer, required - `succeeded` integer, required - `warnings` CommonEvent[], required - `count` integer, required - `firstSeen` V1Time, required - `Time` string, date-time, required - `lastSeen` V1Time, required - `Time` string, date-time, required - `message` string, required - `object` string, required - `objectKind` string - `objectMeta` TypesObjectMeta, required - `annotations` object - `creationTimestamp` V1Time - `Time` string, date-time, required - `labels` object - `name` string - `namespace` string - `uid` string - `objectName` string - `objectNamespace` string - `reason` string, required - `sourceComponent` string, required - `sourceHost` string, required - `type` string, required - `typeMeta` TypesTypeMeta, required - `kind` string - `restartable` boolean - `scalable` boolean - `typeMeta` TypesTypeMeta, required - `kind` string - `restartable` boolean - `scalable` boolean - `errors` Error[], required - unknown - `eventList` CommonEventList, required - `errors` Error[], required - unknown - `events` CommonEvent[], required - `count` integer, required - `firstSeen` V1Time, required - `Time` string, date-time, required - `lastSeen` V1Time, required - `Time` string, date-time, required - `message` string, required - `object` string, required - `objectKind` string - `objectMeta` TypesObjectMeta, required - `annotations` object - `creationTimestamp` V1Time - `Time` string, date-time, required - `labels` object - `name` string - `namespace` string - `uid` string - `objectName` string - `objectNamespace` string - `reason` string, required - `sourceComponent` string, required - `sourceHost` string, required - `type` string, required - `typeMeta` TypesTypeMeta, required - `kind` string - `restartable` boolean - `scalable` boolean - `listMeta` TypesListMeta, required - `totalItems` integer, required - `imagePullSecrets` V1LocalObjectReference[] - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `initContainers` PodContainer[], required - `args` string[], required - `commands` string[], required - `env` PodEnvVar[], required - `name` string, required - `value` string, required - `valueFrom` V1EnvVarSource, required — EnvVarSource represents a source for the value of an EnvVar. - `configMapKeyRef` V1ConfigMapKeySelector — Selects a key from a ConfigMap. - `key` string, required — The key to select. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — Specify whether the ConfigMap or its key must be defined - `fieldRef` V1ObjectFieldSelector — ObjectFieldSelector selects an APIVersioned field of an object. - `apiVersion` string — Version of the schema the FieldPath is written in terms of, defaults to "v1". - `fieldPath` string, required — Path of the field to select in the specified API version. - `resourceFieldRef` V1ResourceFieldSelector — ResourceFieldSelector represents container resources (cpu, memory) and their output format - `containerName` string — Container name: required for volumes, optional for env vars - `divisor` ResourceQuantity - `Format` string, required - `d` ResourceInfDecAmount, required - … - `i` ResourceInt64Amount, required - … - `s` string, required - `resource` string, required — Required: resource to select - `secretKeyRef` V1SecretKeySelector — SecretKeySelector selects a key of a Secret. - `key` string, required — The key of the secret to select from. Must be a valid secret key. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — Specify whether the Secret or its key must be defined - `image` string, required - `livenessProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `name` string, required - `readinessProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `resources` V1ResourceRequirements — ResourceRequirements describes the compute resource requirements. - `claims` V1ResourceClaim[] — Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers. - `name` string, required — Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. - `limits` object — Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `requests` object — Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `securityContext` V1SecurityContext, required — SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext. When both are set, the values in SecurityContext take precedence. - `allowPrivilegeEscalation` boolean — AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN Note that this field cannot be set when spec.os.name is windows. - `appArmorProfile` V1AppArmorProfile — AppArmorProfile defines a pod or container's AppArmor settings. - `localhostProfile` string — localhostProfile indicates a profile loaded on the node that should be used. The profile must be preconfigured on the node to work. Must match the loaded name of the profile. Must be set if and only if type is "Localhost". - `type` string, required — type indicates which kind of AppArmor profile will be applied. Valid options are: Localhost - a profile pre-loaded on the node. RuntimeDefault - the container runtime's default profile. Unconfined - no AppArmor enforcement. - `capabilities` V1Capabilities — Adds and removes POSIX capabilities from running containers. - `add` string[] — Added capabilities - `drop` string[] — Removed capabilities - `privileged` boolean — Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows. - `procMount` string — procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows. - `readOnlyRootFilesystem` boolean — Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows. - `runAsGroup` integer — The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. - `runAsNonRoot` boolean — Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `runAsUser` integer — The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. - `seLinuxOptions` V1SELinuxOptions — SELinuxOptions are the labels to be applied to the container - `level` string — Level is SELinux level label that applies to the container. - `role` string — Role is a SELinux role label that applies to the container. - `type` string — Type is a SELinux type label that applies to the container. - `user` string — User is a SELinux user label that applies to the container. - `seccompProfile` V1SeccompProfile — SeccompProfile defines a pod/container's seccomp profile settings. Only one profile source may be set. - `localhostProfile` string — localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type. - `type` string, required — type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied. - `windowsOptions` V1WindowsSecurityContextOptions — WindowsSecurityContextOptions contain Windows-specific options and credentials. - `gmsaCredentialSpec` string — GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. - `gmsaCredentialSpecName` string — GMSACredentialSpecName is the name of the GMSA credential spec to use. - `hostProcess` boolean — HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true. - `runAsUserName` string — The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `startupProbe` V1Probe, required — Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic. - `exec` V1ExecAction — ExecAction describes a "run in container" action. - `command` string[] — Command is the command line to execute inside the container, the working directory for the command is root ('/') in the container's filesystem. The command is simply exec'd, it is not run inside a shell, so traditional shell instructions ('|', etc) won't work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy. - `failureThreshold` integer — Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. - `grpc` V1GRPCAction - `port` integer, required — Port number of the gRPC service. Number must be in the range 1 to 65535. - `service` string, required — Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC. - `httpGet` V1HTTPGetAction — HTTPGetAction describes an action based on HTTP Get requests. - `host` string — Host name to connect to, defaults to the pod IP. You probably want to set "Host" in httpHeaders instead. - `httpHeaders` V1HTTPHeader[] — Custom headers to set in the request. HTTP allows repeated headers. - `name` string, required — The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header. - `value` string, required — The header field value - `path` string — Path to access on the HTTP server. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `scheme` string — Scheme to use for connecting to the host. Defaults to HTTP. - `initialDelaySeconds` integer — Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `periodSeconds` integer — How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. - `successThreshold` integer — Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. - `tcpSocket` V1TCPSocketAction — TCPSocketAction describes an action based on opening a socket - `host` string — Optional: Host name to connect to, defaults to the pod IP. - `port` IntstrIntOrString, required - `IntVal` integer, required - `StrVal` string, required - `Type` integer, required - `terminationGracePeriodSeconds` integer — Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset. - `timeoutSeconds` integer — Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes - `state` string, required - `status` V1ContainerStatus, required — ContainerStatus contains details for the current status of this container. - `allocatedResources` object — AllocatedResources represents the compute resources allocated for this container by the node. Kubelet sets this value to Container.Resources.Requests upon successful pod admission and after successfully admitting desired pod resize. - `containerID` string — ContainerID is the ID of the container in the format '://'. Where type is a container runtime identifier, returned from Version call of CRI API (for example "containerd"). - `image` string, required — Image is the name of container image that the container is running. The container image may not match the image used in the PodSpec, as it may have been resolved by the runtime. More info: https://kubernetes.io/docs/concepts/containers/images. - `imageID` string, required — ImageID is the image ID of the container's image. The image ID may not match the image ID of the image used in the PodSpec, as it may have been resolved by the runtime. - `lastState` V1ContainerState — ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting. - `running` V1ContainerStateRunning — ContainerStateRunning is a running state of a container. - `startedAt` V1Time - `Time` string, date-time, required - `terminated` V1ContainerStateTerminated — ContainerStateTerminated is a terminated state of a container. - `containerID` string — Container's ID in the format '://' - `exitCode` integer, required — Exit status from the last termination of the container - `finishedAt` V1Time - `Time` string, date-time, required - `message` string — Message regarding the last termination of the container - `reason` string — (brief) reason from the last termination of the container - `signal` integer — Signal from the last termination of the container - `startedAt` V1Time - `Time` string, date-time, required - `waiting` V1ContainerStateWaiting — ContainerStateWaiting is a waiting state of a container. - `message` string — Message regarding why the container is not yet running. - `reason` string — (brief) reason the container is not yet running. - `name` string, required — Name is a DNS_LABEL representing the unique name of the container. Each container in a pod must have a unique name across all container types. Cannot be updated. - `ready` boolean, required — Ready specifies whether the container is currently passing its readiness check. The value will change as readiness probes keep executing. If no readiness probes are specified, this field defaults to true once the container is fully started (see Started field). The value is typically used to determine whether a container is ready to accept traffic. - `resources` V1ResourceRequirements — ResourceRequirements describes the compute resource requirements. - `claims` V1ResourceClaim[] — Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers. - `name` string, required — Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. - `limits` object — Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `requests` object — Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ - `restartCount` integer, required — RestartCount holds the number of times the container has been restarted. Kubelet makes an effort to always increment the value, but there are cases when the state may be lost due to node restarts and then the value may be reset to 0. The value is never negative. - `started` boolean — Started indicates whether the container has finished its postStart lifecycle hook and passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle hook. The null value must be treated the same as false. - `state` V1ContainerState — ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting. - `running` V1ContainerStateRunning — ContainerStateRunning is a running state of a container. - `startedAt` V1Time - `Time` string, date-time, required - `terminated` V1ContainerStateTerminated — ContainerStateTerminated is a terminated state of a container. - `containerID` string — Container's ID in the format '://' - `exitCode` integer, required — Exit status from the last termination of the container - `finishedAt` V1Time - `Time` string, date-time, required - `message` string — Message regarding the last termination of the container - `reason` string — (brief) reason from the last termination of the container - `signal` integer — Signal from the last termination of the container - `startedAt` V1Time - `Time` string, date-time, required - `waiting` V1ContainerStateWaiting — ContainerStateWaiting is a waiting state of a container. - `message` string — Message regarding why the container is not yet running. - `reason` string — (brief) reason the container is not yet running. - `volumeMounts` V1VolumeMountStatus[] — Status of volume mounts. - `mountPath` string, required — MountPath corresponds to the original VolumeMount. - `name` string, required — Name corresponds to the name of the original VolumeMount. - `readOnly` boolean — ReadOnly corresponds to the original VolumeMount. - `recursiveReadOnly` string — RecursiveReadOnly must be set to Disabled, Enabled, or unspecified (for non-readonly mounts). An IfPossible value in the original VolumeMount must be translated to Disabled or Enabled, depending on the mount result. - `volumeMounts` PodVolumeMount[], required - `mountPath` string, required - `name` string, required - `readOnly` boolean, required - `subPath` string, required - `volume` V1Volume, required — Volume represents a named volume in a pod that may be accessed by any container in the pod. - `awsElasticBlockStore` V1AWSElasticBlockStoreVolumeSource — Represents a Persistent Disk resource in AWS. An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `partition` integer — partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). - `readOnly` boolean — readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `volumeID` string, required — volumeID is unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore - `azureDisk` V1AzureDiskVolumeSource — AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod. - `cachingMode` string — cachingMode is the Host Caching mode: None, Read Only, Read Write. - `diskName` string, required — diskName is the Name of the data disk in the blob storage - `diskURI` string, required — diskURI is the URI of data disk in the blob storage - `fsType` string — fsType is Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `kind` string — kind expected values are Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared - `readOnly` boolean — readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `azureFile` V1AzureFileVolumeSource — AzureFile represents an Azure File Service mount on the host and bind mount to the pod. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretName` string, required — secretName is the name of secret that contains Azure Storage Account Name and Key - `shareName` string, required — shareName is the azure share Name - `cephfs` V1CephFSVolumeSource — Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling. - `monitors` string[], required — monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `path` string — path is Optional: Used as the mounted root, rather than the full Ceph tree, default is / - `readOnly` boolean — readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `secretFile` string — secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `user` string — user is optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it - `cinder` V1CinderVolumeSource — Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `volumeID` string, required — volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md - `configMap` V1ConfigMapVolumeSource — Adapts a ConfigMap into a volume. The contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling. - `defaultMode` integer — defaultMode is optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1KeyToPath[] — items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. - `key` string, required — key is the key to project. - `mode` integer — mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `optional` boolean — optional specify whether the ConfigMap or its keys must be defined - `csi` V1CSIVolumeSource — Represents a source location of a volume to mount, managed by an external CSI driver - `driver` string, required — driver is the name of the CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster. - `fsType` string — fsType to mount. Ex. "ext4", "xfs", "ntfs". If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply. - `nodePublishSecretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `readOnly` boolean — readOnly specifies a read-only configuration for the volume. Defaults to false (read/write). - `volumeAttributes` object — volumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver's documentation for supported values. - `downwardAPI` V1DownwardAPIVolumeSource — DownwardAPIVolumeSource represents a volume containing downward API info. Downward API volumes support ownership management and SELinux relabeling. - `defaultMode` integer — Optional: mode bits to use on created files by default. Must be a Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1DownwardAPIVolumeFile[] — Items is a list of downward API volume file - `fieldRef` V1ObjectFieldSelector — ObjectFieldSelector selects an APIVersioned field of an object. - … - `mode` integer — Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..' - `resourceFieldRef` V1ResourceFieldSelector — ResourceFieldSelector represents container resources (cpu, memory) and their output format - … - `emptyDir` V1EmptyDirVolumeSource — Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling. - `medium` string — medium represents what type of storage medium should back this directory. The default is "" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir - `sizeLimit` ResourceQuantity - `Format` string, required - `d` ResourceInfDecAmount, required - … - `i` ResourceInt64Amount, required - … - `s` string, required - `ephemeral` V1EphemeralVolumeSource — Represents an ephemeral volume that is handled by a normal storage driver. - `volumeClaimTemplate` V1PersistentVolumeClaimTemplate — PersistentVolumeClaimTemplate is used to produce PersistentVolumeClaim objects as part of an EphemeralVolumeSource. - `metadata` V1ObjectMeta — ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create. - … - `spec` V1PersistentVolumeClaimSpec, required — PersistentVolumeClaimSpec describes the common attributes of storage devices and allows a Source for provider-specific attributes - … - `fc` V1FCVolumeSource — Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `lun` integer — lun is Optional: FC target lun number - `readOnly` boolean — readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `targetWWNs` string[] — targetWWNs is Optional: FC target worldwide names (WWNs) - `wwids` string[] — wwids Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously. - `flexVolume` V1FlexVolumeSource — FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. - `driver` string, required — driver is the name of the driver to use for this volume. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script. - `options` object — options is Optional: this field holds extra command options if any. - `readOnly` boolean — readOnly is Optional: defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `flocker` V1FlockerVolumeSource — Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling. - `datasetName` string — datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker should be considered as deprecated - `datasetUUID` string — datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset - `gcePersistentDisk` V1GCEPersistentDiskVolumeSource — Represents a Persistent Disk resource in Google Compute Engine. A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling. - `fsType` string — fsType is filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `partition` integer — partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `pdName` string, required — pdName is unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk - `gitRepo` V1GitRepoVolumeSource — Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container. - `directory` string — directory is the target directory name. Must not contain or start with '..'. If '.' is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name. - `repository` string, required — repository is the URL - `revision` string — revision is the commit hash for the specified revision. - `glusterfs` V1GlusterfsVolumeSource — Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling. - `endpoints` string, required — endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `path` string, required — path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `readOnly` boolean — readOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod - `hostPath` V1HostPathVolumeSource — Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling. - `path` string, required — path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath - `type` string — type for HostPath Volume Defaults to "" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath - `iscsi` V1ISCSIVolumeSource — Represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling. - `chapAuthDiscovery` boolean — chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication - `chapAuthSession` boolean — chapAuthSession defines whether support iSCSI Session CHAP authentication - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi - `initiatorName` string — initiatorName is the custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface : will be created for the connection. - `iqn` string, required — iqn is the target iSCSI Qualified Name. - `iscsiInterface` string — iscsiInterface is the interface Name that uses an iSCSI transport. Defaults to 'default' (tcp). - `lun` integer, required — lun represents iSCSI Target Lun number. - `portals` string[] — portals is the iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `targetPortal` string, required — targetPortal is iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). - `name` string, required — name of the volume. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `nfs` V1NFSVolumeSource — Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling. - `path` string, required — path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `readOnly` boolean — readOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `server` string, required — server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs - `persistentVolumeClaim` V1PersistentVolumeClaimVolumeSource — PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system). - `claimName` string, required — claimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims - `readOnly` boolean — readOnly Will force the ReadOnly setting in VolumeMounts. Default false. - `photonPersistentDisk` V1PhotonPersistentDiskVolumeSource — Represents a Photon Controller persistent disk resource. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `pdID` string, required — pdID is the ID that identifies Photon Controller persistent disk - `portworxVolume` V1PortworxVolumeSource — PortworxVolumeSource represents a Portworx volume resource. - `fsType` string — fSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs". Implicitly inferred to be "ext4" if unspecified. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `volumeID` string, required — volumeID uniquely identifies a Portworx volume - `projected` V1ProjectedVolumeSource — Represents a projected volume source - `defaultMode` integer — defaultMode are the mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `sources` V1VolumeProjection[], required — sources is the list of volume projections - `clusterTrustBundle` V1ClusterTrustBundleProjection — ClusterTrustBundleProjection describes how to select a set of ClusterTrustBundle objects and project their contents into the pod filesystem. - … - `configMap` V1ConfigMapProjection — Adapts a ConfigMap into a projected volume. The contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode. - … - `downwardAPI` V1DownwardAPIProjection — Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode. - … - `secret` V1SecretProjection — Adapts a secret into a projected volume. The contents of the target Secret's Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode. - … - `serviceAccountToken` V1ServiceAccountTokenProjection — ServiceAccountTokenProjection represents a projected service account token volume. This projection can be used to insert a service account token into the pods runtime filesystem for use against APIs (Kubernetes API Server or otherwise). - … - `quobyte` V1QuobyteVolumeSource — Represents a Quobyte mount that lasts the lifetime of a pod. Quobyte volumes do not support ownership management or SELinux relabeling. - `group` string — group to map volume access to Default is no group - `readOnly` boolean — readOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false. - `registry` string, required — registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes - `tenant` string — tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin - `user` string — user to map volume access to Defaults to serivceaccount user - `volume` string, required — volume is a string that references an already created Quobyte volume by name. - `rbd` V1RBDVolumeSource — Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling. - `fsType` string — fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd - `image` string, required — image is the rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `keyring` string — keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `monitors` string[], required — monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `pool` string — pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `readOnly` boolean — readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `user` string — user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it - `scaleIO` V1ScaleIOVolumeSource — ScaleIOVolumeSource represents a persistent ScaleIO volume - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Default is "xfs". - `gateway` string, required — gateway is the host address of the ScaleIO API Gateway. - `protectionDomain` string — protectionDomain is the name of the ScaleIO Protection Domain for the configured storage. - `readOnly` boolean — readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference, required — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `sslEnabled` boolean — sslEnabled Flag enable/disable SSL communication with Gateway, default false - `storageMode` string — storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned. - `storagePool` string — storagePool is the ScaleIO Storage Pool associated with the protection domain. - `system` string, required — system is the name of the storage system as configured in ScaleIO. - `volumeName` string — volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source. - `secret` V1SecretVolumeSource — Adapts a Secret into a volume. The contents of the target Secret's Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling. - `defaultMode` integer — defaultMode is Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `items` V1KeyToPath[] — items If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. - `key` string, required — key is the key to project. - `mode` integer — mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. - `path` string, required — path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. - `optional` boolean — optional field specify whether the Secret or its keys must be defined - `secretName` string — secretName is the name of the secret in the pod's namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret - `storageos` V1StorageOSVolumeSource — Represents a StorageOS persistent volume resource. - `fsType` string — fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `readOnly` boolean — readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. - `secretRef` V1LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. - `name` string — Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names - `volumeName` string — volumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace. - `volumeNamespace` string — volumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod's namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to "default" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created. - `vsphereVolume` V1VsphereVirtualDiskVolumeSource — Represents a vSphere volume resource. - `fsType` string — fsType is filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. - `storagePolicyID` string — storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName. - `storagePolicyName` string — storagePolicyName is the storage Policy Based Management (SPBM) profile name. - `volumePath` string, required — volumePath is the path that identifies vSphere volume vmdk - `metrics` ApiMetric[], required - `aggregation` string - `dataPoints` ApiDataPoint[], required - `x` integer, required - `y` integer, required - `metricName` string, required - `metricPoints` ApiMetricPoint[], required - `timestamp` string, date-time, required - `value` integer, required - `nodeName` string, required - `objectMeta` TypesObjectMeta, required - `annotations` object - `creationTimestamp` V1Time - `Time` string, date-time, required - `labels` object - `name` string - `namespace` string - `uid` string - `persistentVolumeClaimList` PersistentvolumeclaimPersistentVolumeClaimList, required - `errors` Error[], required - unknown - `items` PersistentvolumeclaimPersistentVolumeClaim[], required - `accessModes` string[], required - `capacity` object, required - `objectMeta` TypesObjectMeta, required - `annotations` object - `creationTimestamp` V1Time - `Time` string, date-time, required - `labels` object - `name` string - `namespace` string - `uid` string - `status` string, required - `storageClass` string, required - `typeMeta` TypesTypeMeta, required - `kind` string - `restartable` boolean - `scalable` boolean - `volume` string, required - `listMeta` TypesListMeta, required - `totalItems` integer, required - `podIP` string, required - `podPhase` string, required - `qosClass` string, required - `restartCount` integer, required - `securityContext` V1PodSecurityContext, required — PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext. Field values of container.securityContext take precedence over field values of PodSecurityContext. - `appArmorProfile` V1AppArmorProfile — AppArmorProfile defines a pod or container's AppArmor settings. - `localhostProfile` string — localhostProfile indicates a profile loaded on the node that should be used. The profile must be preconfigured on the node to work. Must match the loaded name of the profile. Must be set if and only if type is "Localhost". - `type` string, required — type indicates which kind of AppArmor profile will be applied. Valid options are: Localhost - a profile pre-loaded on the node. RuntimeDefault - the container runtime's default profile. Unconfined - no AppArmor enforcement. - `fsGroup` integer — A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod: 1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR'd with rw-rw - `fsGroupChangePolicy` string — fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used. Note that this field cannot be set when spec.os.name is windows. - `runAsGroup` integer — The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows. - `runAsNonRoot` boolean — Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `runAsUser` integer — The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows. - `seLinuxOptions` V1SELinuxOptions — SELinuxOptions are the labels to be applied to the container - `level` string — Level is SELinux level label that applies to the container. - `role` string — Role is a SELinux role label that applies to the container. - `type` string — Type is a SELinux type label that applies to the container. - `user` string — User is a SELinux user label that applies to the container. - `seccompProfile` V1SeccompProfile — SeccompProfile defines a pod/container's seccomp profile settings. Only one profile source may be set. - `localhostProfile` string — localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type. - `type` string, required — type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied. - `supplementalGroups` integer[] — A list of groups applied to the first process run in each container, in addition to the container's primary GID, the fsGroup (if specified), and group memberships defined in the container image for the uid of the container process. If unspecified, no additional groups are added to any container. Note that group memberships defined in the container image for the uid of the container process are still effective, even if they are not included in this list. Note that this field cannot be set when spec.os.name is windows. - `sysctls` V1Sysctl[] — Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch. Note that this field cannot be set when spec.os.name is windows. - `name` string, required — Name of a property to set - `value` string, required — Value of a property to set - `windowsOptions` V1WindowsSecurityContextOptions — WindowsSecurityContextOptions contain Windows-specific options and credentials. - `gmsaCredentialSpec` string — GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. - `gmsaCredentialSpecName` string — GMSACredentialSpecName is the name of the GMSA credential spec to use. - `hostProcess` boolean — HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true. - `runAsUserName` string — The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. - `serviceAccountName` string, required - `typeMeta` TypesTypeMeta, required - `kind` string - `restartable` boolean - `scalable` boolean --- [API](https://skmtc.net/karmada-io/apis/kubernetes-dashboard-api.md) · [All operations](https://skmtc.net/karmada-io/apis/kubernetes-dashboard-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/karmada-io/kubernetes-dashboard-api/versions/8521b53800a7/schema)