PodStatus constructor
- Input<
Map< ? allocatedResources,String, String> > - Input<
List< ? conditions,PodCondition> > - Input<
List< ? containerStatuses,ContainerStatus> > - Input<
List< ? ephemeralContainerStatuses,ContainerStatus> > - Input<
PodExtendedResourceClaimStatus> ? extendedResourceClaimStatus, - Input<
String> ? hostIP, - Input<
List< ? hostIPs,HostIP> > - Input<
List< ? initContainerStatuses,ContainerStatus> > - Input<
String> ? message, - Input<
List< ? nodeAllocatableResourceClaimStatuses,NodeAllocatableResourceClaimStatus> > - Input<
String> ? nominatedNodeName, - Input<
int> ? observedGeneration, - Input<
String> ? phase, - Input<
String> ? podIP, - Input<
List< ? podIPs,PodIP> > - Input<
String> ? qosClass, - Input<
String> ? reason, - Input<
String> ? resize, - Input<
List< ? resourceClaimStatuses,PodResourceClaimStatus> > - Input<
ResourceRequirements> ? resources, - Input<
String> ? startTime,
Creates a new PodStatus.
allocatedResources AllocatedResources is the total requests allocated for this pod by the node. If pod-level requests are not set, this will be the total requests aggregated across containers in the pod.
conditions Current service state of pod. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions
containerStatuses Statuses of containers in this pod. Each container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status
ephemeralContainerStatuses Statuses for any ephemeral containers that have run in this pod. Each ephemeral container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status
extendedResourceClaimStatus Status of extended resource claim backed by DRA.
hostIP hostIP holds the IP address of the host to which the pod is assigned. Empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns mean that HostIP will not be updated even if there is a node is assigned to pod
hostIPs hostIPs holds the IP addresses allocated to the host. If this field is specified, the first entry must match the hostIP field. This list is empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns means that HostIPs will not be updated even if there is a node is assigned to this pod.
initContainerStatuses Statuses of init containers in this pod. The most recent successful non-restartable init container will have ready = true, the most recently started container will have startTime set. Each init container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-and-container-status
message A human readable message indicating details about why the pod is in this condition.
nodeAllocatableResourceClaimStatuses NodeAllocatableResourceClaimStatuses contains the status of node-allocatable resources that were allocated for this pod through DRA claims. This includes resources currently reported in v1.Node status.allocatable that are not extended resources (see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#extended-resources). Examples include "cpu", "memory", "ephemeral-storage", and hugepages.
nominatedNodeName nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.
observedGeneration If set, this represents the .metadata.generation that the pod status was set based upon. The PodObservedGenerationTracking feature gate must be enabled to use this field.
phase The phase of a Pod is a simple, high-level summary of where the Pod is in its lifecycle. The conditions array, the reason and message fields, and the individual container status arrays contain more detail about the pod's status. There are five possible phase values:
podIP podIP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.
podIPs podIPs holds the IP addresses allocated to the pod. If this field is specified, the 0th entry must match the podIP field. Pods may be allocated at most 1 value for each of IPv4 and IPv6. This list is empty if no IPs have been allocated yet.
qosClass The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#quality-of-service-classes
reason A brief CamelCase message indicating details about why the pod is in this state. e.g. 'Evicted'
resize Status of resources resize desired for pod's containers. It is empty if no resources resize is pending. Any changes to container resources will automatically set this to "Proposed" Deprecated: Resize status is moved to two pod conditions PodResizePending and PodResizeInProgress. PodResizePending will track states where the spec has been resized, but the Kubelet has not yet allocated the resources. PodResizeInProgress will track in-progress resizes, and should be present whenever allocated resources != acknowledged resources.
resourceClaimStatuses Status of resource claims.
resources Resources represents the compute resource requests and limits that have been applied at the pod level if pod-level requests or limits are set in PodSpec.Resources
startTime RFC 3339 date and time at which the object was acknowledged by the Kubelet. This is before the Kubelet pulled the container image(s) for the pod.
Implementation
const PodStatus({
this.allocatedResources,
this.conditions,
this.containerStatuses,
this.ephemeralContainerStatuses,
this.extendedResourceClaimStatus,
this.hostIP,
this.hostIPs,
this.initContainerStatuses,
this.message,
this.nodeAllocatableResourceClaimStatuses,
this.nominatedNodeName,
this.observedGeneration,
this.phase,
this.podIP,
this.podIPs,
this.qosClass,
this.reason,
this.resize,
this.resourceClaimStatuses,
this.resources,
this.startTime,
});