|
3784 | 3784 | "description": "The number of pods which reached phase Succeeded.", |
3785 | 3785 | "format": "int32", |
3786 | 3786 | "type": "integer" |
| 3787 | + }, |
| 3788 | + "uncountedTerminatedPods": { |
| 3789 | + "$ref": "#/definitions/io.k8s.api.batch.v1.UncountedTerminatedPods", |
| 3790 | + "description": "UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.\n\nThe job controller creates pods with a finalizer. When a pod terminates (succeeded or failed), the controller does three steps to account for it in the job status: (1) Add the pod UID to the arrays in this field. (2) Remove the pod finalizer. (3) Remove the pod UID from the arrays while increasing the corresponding\n counter.\n\nThis field is alpha-level. The job controller only makes use of this field when the feature gate PodTrackingWithFinalizers is enabled. Old jobs might not be tracked using this field, in which case the field remains null." |
3787 | 3791 | } |
3788 | 3792 | }, |
3789 | 3793 | "type": "object" |
|
3802 | 3806 | }, |
3803 | 3807 | "type": "object" |
3804 | 3808 | }, |
| 3809 | + "io.k8s.api.batch.v1.UncountedTerminatedPods": { |
| 3810 | + "description": "UncountedTerminatedPods holds UIDs of Pods that have terminated but haven't been accounted in Job status counters.", |
| 3811 | + "properties": { |
| 3812 | + "failed": { |
| 3813 | + "description": "Failed holds UIDs of failed Pods.", |
| 3814 | + "items": { |
| 3815 | + "type": "string" |
| 3816 | + }, |
| 3817 | + "type": "array", |
| 3818 | + "x-kubernetes-list-type": "set" |
| 3819 | + }, |
| 3820 | + "succeeded": { |
| 3821 | + "description": "Succeeded holds UIDs of succeeded Pods.", |
| 3822 | + "items": { |
| 3823 | + "type": "string" |
| 3824 | + }, |
| 3825 | + "type": "array", |
| 3826 | + "x-kubernetes-list-type": "set" |
| 3827 | + } |
| 3828 | + }, |
| 3829 | + "type": "object" |
| 3830 | + }, |
3805 | 3831 | "io.k8s.api.batch.v1beta1.CronJob": { |
3806 | 3832 | "description": "CronJob represents the configuration of a single cron job.", |
3807 | 3833 | "properties": { |
|
4878 | 4904 | ] |
4879 | 4905 | }, |
4880 | 4906 | "io.k8s.api.core.v1.ConfigMapNodeConfigSource": { |
4881 | | - "description": "ConfigMapNodeConfigSource contains the information to reference a ConfigMap as a config source for the Node.", |
| 4907 | + "description": "ConfigMapNodeConfigSource contains the information to reference a ConfigMap as a config source for the Node. This API is deprecated since 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration", |
4882 | 4908 | "properties": { |
4883 | 4909 | "kubeletConfigKey": { |
4884 | 4910 | "description": "KubeletConfigKey declares which key of the referenced ConfigMap corresponds to the KubeletConfiguration structure This field is required in all cases.", |
|
6793 | 6819 | "type": "object" |
6794 | 6820 | }, |
6795 | 6821 | "io.k8s.api.core.v1.NodeConfigSource": { |
6796 | | - "description": "NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil.", |
| 6822 | + "description": "NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil. This API is deprecated since 1.22", |
6797 | 6823 | "properties": { |
6798 | 6824 | "configMap": { |
6799 | 6825 | "$ref": "#/definitions/io.k8s.api.core.v1.ConfigMapNodeConfigSource", |
|
6940 | 6966 | "properties": { |
6941 | 6967 | "configSource": { |
6942 | 6968 | "$ref": "#/definitions/io.k8s.api.core.v1.NodeConfigSource", |
6943 | | - "description": "If specified, the source to get node configuration from The DynamicKubeletConfig feature gate must be enabled for the Kubelet to use this field" |
| 6969 | + "description": "Deprecated. If specified, the source of the node's configuration. The DynamicKubeletConfig feature gate must be enabled for the Kubelet to use this field. This field is deprecated as of 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration" |
6944 | 6970 | }, |
6945 | 6971 | "externalID": { |
6946 | 6972 | "description": "Deprecated. Not all kubelets will set this field. Remove field after 1.13. see: https://issues.k8s.io/61966", |
|
7316 | 7342 | }, |
7317 | 7343 | "dataSource": { |
7318 | 7344 | "$ref": "#/definitions/io.k8s.api.core.v1.TypedLocalObjectReference", |
7319 | | - "description": "This field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) * An existing custom resource that implements data population (Alpha) In order to use custom resource types that implement data population, the AnyVolumeDataSource feature gate must be enabled. If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source." |
| 7345 | + "description": "This field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. If the AnyVolumeDataSource feature gate is enabled, this field will always have the same contents as the DataSourceRef field." |
| 7346 | + }, |
| 7347 | + "dataSourceRef": { |
| 7348 | + "$ref": "#/definitions/io.k8s.api.core.v1.TypedLocalObjectReference", |
| 7349 | + "description": "Specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any local object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the DataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, both fields (DataSource and DataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. There are two important differences between DataSource and DataSourceRef: * While DataSource only allows two specific types of objects, DataSourceRef\n allows any non-core object, as well as PersistentVolumeClaim objects.\n* While DataSource ignores disallowed values (dropping them), DataSourceRef\n preserves all values, and generates an error if a disallowed value is\n specified.\n(Alpha) Using this field requires the AnyVolumeDataSource feature gate to be enabled." |
7320 | 7350 | }, |
7321 | 7351 | "resources": { |
7322 | 7352 | "$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements", |
|
9512 | 9542 | "description": "ServiceSpec describes the attributes that a user creates on a service.", |
9513 | 9543 | "properties": { |
9514 | 9544 | "allocateLoadBalancerNodePorts": { |
9515 | | - "description": "allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer. Default is \"true\". It may be set to \"false\" if the cluster load-balancer does not rely on NodePorts. allocateLoadBalancerNodePorts may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type. This field is alpha-level and is only honored by servers that enable the ServiceLBNodePortControl feature.", |
| 9545 | + "description": "allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer. Default is \"true\". It may be set to \"false\" if the cluster load-balancer does not rely on NodePorts. If the caller requests specific NodePorts (by specifying a value), those requests will be respected, regardless of this field. This field may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type. This field is beta-level and is only honored by servers that enable the ServiceLBNodePortControl feature.", |
9516 | 9546 | "type": "boolean" |
9517 | 9547 | }, |
9518 | 9548 | "clusterIP": { |
|
0 commit comments