|
3770 | 3770 | }, |
3771 | 3771 | "uncountedTerminatedPods": { |
3772 | 3772 | "$ref": "#/definitions/io.k8s.api.batch.v1.UncountedTerminatedPods", |
3773 | | - "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 JobTrackingWithFinalizers is enabled. Old jobs might not be tracked using this field, in which case the field remains null." |
| 3773 | + "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 beta-level. The job controller only makes use of this field when the feature gate JobTrackingWithFinalizers is enabled (enabled by default). Old jobs might not be tracked using this field, in which case the field remains null." |
3774 | 3774 | } |
3775 | 3775 | }, |
3776 | 3776 | "type": "object" |
|
5575 | 5575 | "type": "object" |
5576 | 5576 | }, |
5577 | 5577 | "io.k8s.api.core.v1.EphemeralContainer": { |
5578 | | - "description": "An EphemeralContainer is a container that may be added temporarily to an existing pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a pod is removed or restarted. If an ephemeral container causes a pod to exceed its resource allocation, the pod may be evicted. Ephemeral containers may not be added by directly updating the pod spec. They must be added via the pod's ephemeralcontainers subresource, and they will appear in the pod spec once added. This is an alpha feature enabled by the EphemeralContainers feature flag.", |
| 5578 | + "description": "An EphemeralContainer is a temporary container that you may add to an existing Pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a Pod is removed or restarted. The kubelet may evict a Pod if an ephemeral container causes the Pod to exceed its resource allocation.\n\nTo add an ephemeral container, use the ephemeralcontainers subresource of an existing Pod. Ephemeral containers may not be removed or restarted.\n\nThis is a beta feature available on clusters that haven't disabled the EphemeralContainers feature gate.", |
5579 | 5579 | "properties": { |
5580 | 5580 | "args": { |
5581 | 5581 | "description": "Arguments to the entrypoint. The docker image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell", |
|
5632 | 5632 | "items": { |
5633 | 5633 | "$ref": "#/definitions/io.k8s.api.core.v1.ContainerPort" |
5634 | 5634 | }, |
5635 | | - "type": "array" |
| 5635 | + "type": "array", |
| 5636 | + "x-kubernetes-list-map-keys": [ |
| 5637 | + "containerPort", |
| 5638 | + "protocol" |
| 5639 | + ], |
| 5640 | + "x-kubernetes-list-type": "map", |
| 5641 | + "x-kubernetes-patch-merge-key": "containerPort", |
| 5642 | + "x-kubernetes-patch-strategy": "merge" |
5636 | 5643 | }, |
5637 | 5644 | "readinessProbe": { |
5638 | 5645 | "$ref": "#/definitions/io.k8s.api.core.v1.Probe", |
|
5659 | 5666 | "type": "boolean" |
5660 | 5667 | }, |
5661 | 5668 | "targetContainerName": { |
5662 | | - "description": "If set, the name of the container from PodSpec that this ephemeral container targets. The ephemeral container will be run in the namespaces (IPC, PID, etc) of this container. If not set then the ephemeral container is run in whatever namespaces are shared for the pod. Note that the container runtime must support this feature.", |
| 5669 | + "description": "If set, the name of the container from PodSpec that this ephemeral container targets. The ephemeral container will be run in the namespaces (IPC, PID, etc) of this container. If not set then the ephemeral container uses the namespaces configured in the Pod spec.\n\nThe container runtime must implement support for this feature. If the runtime does not support namespace targeting then the result of setting this field is undefined.", |
5663 | 5670 | "type": "string" |
5664 | 5671 | }, |
5665 | 5672 | "terminationMessagePath": { |
|
5684 | 5691 | "x-kubernetes-patch-strategy": "merge" |
5685 | 5692 | }, |
5686 | 5693 | "volumeMounts": { |
5687 | | - "description": "Pod volumes to mount into the container's filesystem. Cannot be updated.", |
| 5694 | + "description": "Pod volumes to mount into the container's filesystem. Subpath mounts are not allowed for ephemeral containers. Cannot be updated.", |
5688 | 5695 | "items": { |
5689 | 5696 | "$ref": "#/definitions/io.k8s.api.core.v1.VolumeMount" |
5690 | 5697 | }, |
|
7962 | 7969 | "type": "boolean" |
7963 | 7970 | }, |
7964 | 7971 | "ephemeralContainers": { |
7965 | | - "description": "List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod's ephemeralcontainers subresource. This field is alpha-level and is only honored by servers that enable the EphemeralContainers feature.", |
| 7972 | + "description": "List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod's ephemeralcontainers subresource. This field is beta-level and available on clusters that haven't disabled the EphemeralContainers feature gate.", |
7966 | 7973 | "items": { |
7967 | 7974 | "$ref": "#/definitions/io.k8s.api.core.v1.EphemeralContainer" |
7968 | 7975 | }, |
|
8149 | 8156 | "type": "array" |
8150 | 8157 | }, |
8151 | 8158 | "ephemeralContainerStatuses": { |
8152 | | - "description": "Status for any ephemeral containers that have run in this pod. This field is alpha-level and is only populated by servers that enable the EphemeralContainers feature.", |
| 8159 | + "description": "Status for any ephemeral containers that have run in this pod. This field is beta-level and available on clusters that haven't disabled the EphemeralContainers feature gate.", |
8153 | 8160 | "items": { |
8154 | 8161 | "$ref": "#/definitions/io.k8s.api.core.v1.ContainerStatus" |
8155 | 8162 | }, |
|
0 commit comments