diff --git a/master-local/_definitions.json b/master-local/_definitions.json
index c1b7b79af86782c022d34be5e7f85c23b4327271..2f974d1643996e53db21ec55541b4ff086bffda5 100644
--- a/master-local/_definitions.json
+++ b/master-local/_definitions.json
@@ -9513,6 +9513,11 @@
"description": "Human-readable message indicating details about last transition.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": "string"
@@ -10105,6 +10110,11 @@
"description": "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.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": "string"
diff --git a/master-local/podcondition-v1.json b/master-local/podcondition-v1.json
index 3758351b04337c96a7a7dbfae62e5a234d8a530f..bfb1ea35fd5639f3573ab1f86913cacab647f6e3 100644
--- a/master-local/podcondition-v1.json
+++ b/master-local/podcondition-v1.json
@@ -16,6 +16,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-local/podcondition.json b/master-local/podcondition.json
index 3758351b04337c96a7a7dbfae62e5a234d8a530f..bfb1ea35fd5639f3573ab1f86913cacab647f6e3 100644
--- a/master-local/podcondition.json
+++ b/master-local/podcondition.json
@@ -16,6 +16,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-local/podstatus-v1.json b/master-local/podstatus-v1.json
index 5ba48a50441ccbfeed9edf30044aa90ee42ff7e7..1032637cf84c391f3edca94ab779c43d77a3de89 100644
--- a/master-local/podstatus-v1.json
+++ b/master-local/podstatus-v1.json
@@ -84,6 +84,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-local/podstatus.json b/master-local/podstatus.json
index 5ba48a50441ccbfeed9edf30044aa90ee42ff7e7..1032637cf84c391f3edca94ab779c43d77a3de89 100644
--- a/master-local/podstatus.json
+++ b/master-local/podstatus.json
@@ -84,6 +84,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/_definitions.json b/master-standalone-strict/_definitions.json
index 82babb87be3fa4e198d9826da5a6c628539164f7..c2f47b63b3650f0a29a009162b4fbfb78ff04228 100644
--- a/master-standalone-strict/_definitions.json
+++ b/master-standalone-strict/_definitions.json
@@ -9822,6 +9822,11 @@
"description": "Human-readable message indicating details about last transition.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": "string"
@@ -10426,6 +10431,11 @@
"description": "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.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": "string"
diff --git a/master-standalone-strict/pod-v1.json b/master-standalone-strict/pod-v1.json
index 876e806cb7f69011a8b6318afcf8343e5aaf07f5..9b9ccb70212c99d97c0baefdb6890226ba151800 100644
--- a/master-standalone-strict/pod-v1.json
+++ b/master-standalone-strict/pod-v1.json
@@ -10533,6 +10533,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -12319,6 +12327,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/pod.json b/master-standalone-strict/pod.json
index 3d7706e4744d05f0456c6023b8194708c0ec7a9c..fdddb9d2c2c1c30d3c04273a4ff95b61aa56ede9 100644
--- a/master-standalone-strict/pod.json
+++ b/master-standalone-strict/pod.json
@@ -10530,6 +10530,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -12316,6 +12324,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/podcondition-v1.json b/master-standalone-strict/podcondition-v1.json
index 600670b716543697ef15d185b2edfe1735221000..c7745c0cfd537941b2663df1ef9e645ccf96f02e 100644
--- a/master-standalone-strict/podcondition-v1.json
+++ b/master-standalone-strict/podcondition-v1.json
@@ -24,6 +24,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-standalone-strict/podcondition.json b/master-standalone-strict/podcondition.json
index 600670b716543697ef15d185b2edfe1735221000..c7745c0cfd537941b2663df1ef9e645ccf96f02e 100644
--- a/master-standalone-strict/podcondition.json
+++ b/master-standalone-strict/podcondition.json
@@ -24,6 +24,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-standalone-strict/podlist-v1.json b/master-standalone-strict/podlist-v1.json
index 706bd607a5b409d6e5b24dfe3265677720b3a5d6..b066ba4a501dc7c3f5d8f2e5728d30325fd099bc 100644
--- a/master-standalone-strict/podlist-v1.json
+++ b/master-standalone-strict/podlist-v1.json
@@ -10548,6 +10548,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -12334,6 +12342,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/podlist.json b/master-standalone-strict/podlist.json
index edd7f7503d8b8a6bd3b47465ff336addf53af0dd..6006652f56ee9d45db0630fd79f296fb5bbf8058 100644
--- a/master-standalone-strict/podlist.json
+++ b/master-standalone-strict/podlist.json
@@ -10542,6 +10542,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -12328,6 +12336,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/podstatus-v1.json b/master-standalone-strict/podstatus-v1.json
index da9036f868312e0de3f94a96b5b84141dbf1e996..06ba2b92cb02550dcb6da85ffa6d8b3e5059b939 100644
--- a/master-standalone-strict/podstatus-v1.json
+++ b/master-standalone-strict/podstatus-v1.json
@@ -29,6 +29,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -1815,6 +1823,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone-strict/podstatus.json b/master-standalone-strict/podstatus.json
index da9036f868312e0de3f94a96b5b84141dbf1e996..06ba2b92cb02550dcb6da85ffa6d8b3e5059b939 100644
--- a/master-standalone-strict/podstatus.json
+++ b/master-standalone-strict/podstatus.json
@@ -29,6 +29,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -1815,6 +1823,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/_definitions.json b/master-standalone/_definitions.json
index c1b7b79af86782c022d34be5e7f85c23b4327271..2f974d1643996e53db21ec55541b4ff086bffda5 100644
--- a/master-standalone/_definitions.json
+++ b/master-standalone/_definitions.json
@@ -9513,6 +9513,11 @@
"description": "Human-readable message indicating details about last transition.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": "string"
@@ -10105,6 +10110,11 @@
"description": "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.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": "string"
diff --git a/master-standalone/pod-v1.json b/master-standalone/pod-v1.json
index 06b08a14167b41c95e8d24a7d02c59b52d466155..8e856fc2f65403e1edc22454704620d38715170a 100644
--- a/master-standalone/pod-v1.json
+++ b/master-standalone/pod-v1.json
@@ -10249,6 +10249,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -11985,6 +11993,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/pod.json b/master-standalone/pod.json
index 88e0fef84a995cb99af5b4e8f820af226c35a064..0a60f0227579d6319fb929db9dfc9bbe5d8ff3f4 100644
--- a/master-standalone/pod.json
+++ b/master-standalone/pod.json
@@ -10246,6 +10246,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -11982,6 +11990,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/podcondition-v1.json b/master-standalone/podcondition-v1.json
index a4579d8a7f93977e7f9898299d1d1a5d6268f933..eea49ff284a071d4e2e57a46b4c30c5d34d04684 100644
--- a/master-standalone/podcondition-v1.json
+++ b/master-standalone/podcondition-v1.json
@@ -24,6 +24,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-standalone/podcondition.json b/master-standalone/podcondition.json
index a4579d8a7f93977e7f9898299d1d1a5d6268f933..eea49ff284a071d4e2e57a46b4c30c5d34d04684 100644
--- a/master-standalone/podcondition.json
+++ b/master-standalone/podcondition.json
@@ -24,6 +24,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master-standalone/podlist-v1.json b/master-standalone/podlist-v1.json
index b7595c8b23ecc92d57f676f50050982ab9b2c985..cc6c117c6eadfecafa08716ef2e5f64654fb249d 100644
--- a/master-standalone/podlist-v1.json
+++ b/master-standalone/podlist-v1.json
@@ -10264,6 +10264,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -12000,6 +12008,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/podlist.json b/master-standalone/podlist.json
index e60bd84d6b849407176b63cfcc2e7426770b9b99..25abb606fe7ccf9421b55c74c8c39a7180918f31 100644
--- a/master-standalone/podlist.json
+++ b/master-standalone/podlist.json
@@ -10258,6 +10258,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -11994,6 +12002,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/podstatus-v1.json b/master-standalone/podstatus-v1.json
index 46b66cd9c4d5c60e7b8b29d817f08d73c0c1864a..ab49a4dd2ce936435a72ee546e267809316e29fb 100644
--- a/master-standalone/podstatus-v1.json
+++ b/master-standalone/podstatus-v1.json
@@ -29,6 +29,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -1765,6 +1773,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master-standalone/podstatus.json b/master-standalone/podstatus.json
index 46b66cd9c4d5c60e7b8b29d817f08d73c0c1864a..ab49a4dd2ce936435a72ee546e267809316e29fb 100644
--- a/master-standalone/podstatus.json
+++ b/master-standalone/podstatus.json
@@ -29,6 +29,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
@@ -1765,6 +1773,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master/_definitions.json b/master/_definitions.json
index c1b7b79af86782c022d34be5e7f85c23b4327271..2f974d1643996e53db21ec55541b4ff086bffda5 100644
--- a/master/_definitions.json
+++ b/master/_definitions.json
@@ -9513,6 +9513,11 @@
"description": "Human-readable message indicating details about last transition.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": "string"
@@ -10105,6 +10110,11 @@
"description": "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.",
"type": "string"
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": "integer"
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": "string"
diff --git a/master/podcondition-v1.json b/master/podcondition-v1.json
index e9427f4cfbd76882c88a44cff5fb741bf124d590..ac6dfe9e976714cf5dbc19b5dcce7f506625f4dd 100644
--- a/master/podcondition-v1.json
+++ b/master/podcondition-v1.json
@@ -16,6 +16,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master/podcondition.json b/master/podcondition.json
index e9427f4cfbd76882c88a44cff5fb741bf124d590..ac6dfe9e976714cf5dbc19b5dcce7f506625f4dd 100644
--- a/master/podcondition.json
+++ b/master/podcondition.json
@@ -16,6 +16,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod condition was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"reason": {
"description": "Unique, one-word, CamelCase reason for the condition's last transition.",
"type": [
diff --git a/master/podstatus-v1.json b/master/podstatus-v1.json
index 16eeafe747adb7e1eb2bdfb142e2c7b1b54e745f..8badf0bcb8506b2acd159eb2ed991ca392a5592c 100644
--- a/master/podstatus-v1.json
+++ b/master/podstatus-v1.json
@@ -84,6 +84,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [
diff --git a/master/podstatus.json b/master/podstatus.json
index 16eeafe747adb7e1eb2bdfb142e2c7b1b54e745f..8badf0bcb8506b2acd159eb2ed991ca392a5592c 100644
--- a/master/podstatus.json
+++ b/master/podstatus.json
@@ -84,6 +84,14 @@
"null"
]
},
+ "observedGeneration": {
+ "description": "If set, this represents the .metadata.generation that the pod status was set based upon. This is an alpha field. Enable PodObservedGenerationTracking to be able to use this field.",
+ "format": "int64",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
"phase": {
"description": "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:\n\nPending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
"type": [