[skip ci] repo-sync

gen/models/V1DeleteOptions.ts

@@ -30,6 +30,10 @@ export class V1DeleteOptions {
     */
     'gracePeriodSeconds'?: number;
     /**
+    * if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it
+    */
+    'ignoreStoreReadErrorWithClusterBreakingPotential'?: boolean;
+    /**
     * Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
     */
     'kind'?: string;
@@ -64,6 +68,12 @@ export class V1DeleteOptions {
             "type": "number",
             "format": "int64"
         },
+        {
+            "name": "ignoreStoreReadErrorWithClusterBreakingPotential",
+            "baseName": "ignoreStoreReadErrorWithClusterBreakingPotential",
+            "type": "boolean",
+            "format": ""
+        },
         {
             "name": "kind",
             "baseName": "kind",

gen/models/V1GRPCAction.ts

@@ -12,6 +12,9 @@
 
 
 
+/**
+* GRPCAction specifies an action involving a GRPC service.
+*/
 export class V1GRPCAction {
     /**
     * Port number of the gRPC service. Number must be in the range 1 to 65535.

gen/models/V1PersistentVolumeClaimCondition.ts

@@ -32,7 +32,13 @@ export class V1PersistentVolumeClaimCondition {
     * reason is a unique, this should be a short, machine understandable string that gives the reason for condition\'s last transition. If it reports \"Resizing\" that means the underlying persistent volume is being resized.
     */
     'reason'?: string;
+    /**
+    * Status is the status of the condition. Can be True, False, Unknown. More info: https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1/#:~:text=state%20of%20pvc-,conditions.status,-(string)%2C%20required
+    */
     'status': string;
+    /**
+    * Type is the type of the condition. More info: https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1/#:~:text=set%20to%20%27ResizeStarted%27.-,PersistentVolumeClaimCondition,-contains%20details%20about
+    */
     'type': string;
 
     static readonly discriminator: string | undefined = undefined;

gen/models/V1PodDNSConfigOption.ts

@@ -17,9 +17,12 @@
 */
 export class V1PodDNSConfigOption {
     /**
-    * Required.
+    * Name is this DNS resolver option\'s name. Required.
     */
     'name'?: string;
+    /**
+    * Value is this DNS resolver option\'s value.
+    */
     'value'?: string;
 
     static readonly discriminator: string | undefined = undefined;

gen/models/V1PodSecurityContext.ts

@@ -42,6 +42,10 @@ export class V1PodSecurityContext {
     * 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.
     */
     'runAsUser'?: number;
+    /**
+    * seLinuxChangePolicy defines how the container\'s SELinux label is applied to all volumes used by the Pod. It has no effect on nodes that do not support SELinux or to volumes does not support SELinux. Valid values are \"MountOption\" and \"Recursive\".  \"Recursive\" means relabeling of all files on all Pod volumes by the container runtime. This may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node.  \"MountOption\" mounts all eligible Pod volumes with `-o context` mount option. This requires all Pods that share the same volume to use the same SELinux label. It is not possible to share the same volume among privileged and unprivileged Pods. Eligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes whose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their CSIDriver instance. Other volumes are always re-labelled recursively. \"MountOption\" value is allowed only when SELinuxMount feature gate is enabled.  If not specified and SELinuxMount feature gate is enabled, \"MountOption\" is used. If not specified and SELinuxMount feature gate is disabled, \"MountOption\" is used for ReadWriteOncePod volumes and \"Recursive\" for all other volumes.  This field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers.  All Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state. Note that this field cannot be set when spec.os.name is windows.
+    */
+    'seLinuxChangePolicy'?: string;
     'seLinuxOptions'?: V1SELinuxOptions;
     'seccompProfile'?: V1SeccompProfile;
     /**
@@ -97,6 +101,12 @@ export class V1PodSecurityContext {
             "type": "number",
             "format": "int64"
         },
+        {
+            "name": "seLinuxChangePolicy",
+            "baseName": "seLinuxChangePolicy",
+            "type": "string",
+            "format": ""
+        },
         {
             "name": "seLinuxOptions",
             "baseName": "seLinuxOptions",

gen/models/V1PodSpec.ts

@@ -21,6 +21,7 @@ import { V1PodReadinessGate } from '../models/V1PodReadinessGate';
 import { V1PodResourceClaim } from '../models/V1PodResourceClaim';
 import { V1PodSchedulingGate } from '../models/V1PodSchedulingGate';
 import { V1PodSecurityContext } from '../models/V1PodSecurityContext';
+import { V1ResourceRequirements } from '../models/V1ResourceRequirements';
 import { V1Toleration } from '../models/V1Toleration';
 import { V1TopologySpreadConstraint } from '../models/V1TopologySpreadConstraint';
 import { V1Volume } from '../models/V1Volume';
@@ -121,6 +122,7 @@ export class V1PodSpec {
     * ResourceClaims defines which ResourceClaims must be allocated and reserved before the Pod is allowed to start. The resources will be made available to those containers which consume them by name.  This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.  This field is immutable.
     */
     'resourceClaims'?: Array<V1PodResourceClaim>;
+    'resources'?: V1ResourceRequirements;
     /**
     * Restart policy for all containers within the pod. One of Always, OnFailure, Never. In some contexts, only a subset of those values may be permitted. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy  Possible enum values:  - `\"Always\"`  - `\"Never\"`  - `\"OnFailure\"`
     */
@@ -328,6 +330,12 @@ export class V1PodSpec {
             "type": "Array<V1PodResourceClaim>",
             "format": ""
         },
+        {
+            "name": "resources",
+            "baseName": "resources",
+            "type": "V1ResourceRequirements",
+            "format": ""
+        },
         {
             "name": "restartPolicy",
             "baseName": "restartPolicy",

gen/models/V1PodStatus.ts

@@ -26,11 +26,11 @@ export class V1PodStatus {
     */
     'conditions'?: Array<V1PodCondition>;
     /**
-    * The list has one entry per container in the manifest. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status
+    * 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
     */
     'containerStatuses'?: Array<V1ContainerStatus>;
     /**
-    * Status for any ephemeral containers that have run in this pod.
+    * 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
     */
     'ephemeralContainerStatuses'?: Array<V1ContainerStatus>;
     /**
@@ -42,7 +42,7 @@ export class V1PodStatus {
     */
     'hostIPs'?: Array<V1HostIP>;
     /**
-    * The list has one entry per init container in the manifest. The most recent successful init container will have ready = true, the most recently started container will have startTime set. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status
+    * 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
     */
     'initContainerStatuses'?: Array<V1ContainerStatus>;
     /**

gen/models/V1ResourceHealth.ts

@@ -13,7 +13,7 @@
 
 
 /**
-* ResourceHealth represents the health of a resource. It has the latest device health information. This is a part of KEP https://kep.k8s.io/4680 and historical health changes are planned to be added in future iterations of a KEP.
+* ResourceHealth represents the health of a resource. It has the latest device health information. This is a part of KEP https://kep.k8s.io/4680.
 */
 export class V1ResourceHealth {
     /**

gen/models/V1ResourceStatus.ts

@@ -13,13 +13,16 @@
 import { V1ResourceHealth } from '../models/V1ResourceHealth';
 
 
+/**
+* ResourceStatus represents the status of a single resource allocated to a Pod.
+*/
 export class V1ResourceStatus {
     /**
-    * Name of the resource. Must be unique within the pod and match one of the resources from the pod spec.
+    * Name of the resource. Must be unique within the pod and in case of non-DRA resource, match one of the resources from the pod spec. For DRA resources, the value must be \"claim:<claim_name>/<request>\". When this status is reported about a container, the \"claim_name\" and \"request\" must match one of the claims of this container.
     */
     'name': string;
     /**
-    * List of unique Resources health. Each element in the list contains an unique resource ID and resource health. At a minimum, ResourceID must uniquely identify the Resource allocated to the Pod on the Node for the lifetime of a Pod. See ResourceID type for it\'s definition.
+    * List of unique resources health. Each element in the list contains an unique resource ID and its health. At a minimum, for the lifetime of a Pod, resource ID must uniquely identify the resource allocated to the Pod on the Node. If other Pod on the same Node reports the status with the same resource ID, it must be the same resource they share. See ResourceID type definition for a specific format it has in various use cases.
     */
     'resources'?: Array<V1ResourceHealth>;
 

gen/models/V1TypedObjectReference.ts

@@ -12,6 +12,9 @@
 
 
 
+/**
+* TypedObjectReference contains enough information to let you locate the typed referenced object
+*/
 export class V1TypedObjectReference {
     /**
     * APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.