coreos/prometheus-operator
1
0
Fork 0
mirror of https://github.com/coreos/prometheus-operator.git synced 2026-02-05 06:45:27 +01:00
Code Issues Releases Wiki Activity

chore: update go dependencies

Browse Source 
Signed-off-by: Jayapriya Pai <slashpai9@gmail.com>
This commit is contained in:
Jayapriya Pai
2024-12-12 12:51:17 +05:30
parent 020f43bc05
commit 4261909d36
22 changed files with 2151 additions and 1487 deletions
Download Patch File Download Diff File Expand all files Collapse all files

123
jsonnet/prometheus-operator/alertmanagers-crd.json
View File

@@ -2080,7 +2080,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2094,7 +2094,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2150,7 +2150,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2164,7 +2164,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2195,7 +2195,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2209,7 +2209,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2265,7 +2265,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2279,7 +2279,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2313,7 +2313,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2332,7 +2332,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2351,7 +2351,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2422,7 +2422,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2508,7 +2508,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2527,7 +2527,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2546,7 +2546,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2617,7 +2617,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2886,7 +2886,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2905,7 +2905,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2924,7 +2924,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2995,7 +2995,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3479,7 +3479,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3493,7 +3493,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3549,7 +3549,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -3563,7 +3563,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3594,7 +3594,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3608,7 +3608,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3664,7 +3664,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -3678,7 +3678,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3712,7 +3712,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3731,7 +3731,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3750,7 +3750,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3821,7 +3821,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3907,7 +3907,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3926,7 +3926,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3945,7 +3945,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -4016,7 +4016,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -4285,7 +4285,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -4304,7 +4304,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -4323,7 +4323,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -4394,7 +4394,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -4736,6 +4736,10 @@
"format": "int64",
"type": "integer"
},
"seLinuxChangePolicy": {
"description": "seLinuxChangePolicy defines how the container's SELinux label is applied to all volumes used by the Pod.\nIt has no effect on nodes that do not support SELinux or to volumes does not support SELinux.\nValid values are \"MountOption\" and \"Recursive\".\n\n\"Recursive\" means relabeling of all files on all Pod volumes by the container runtime.\nThis may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node.\n\n\"MountOption\" mounts all eligible Pod volumes with `-o context` mount option.\nThis requires all Pods that share the same volume to use the same SELinux label.\nIt is not possible to share the same volume among privileged and unprivileged Pods.\nEligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes\nwhose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their\nCSIDriver instance. Other volumes are always re-labelled recursively.\n\"MountOption\" value is allowed only when SELinuxMount feature gate is enabled.\n\nIf not specified and SELinuxMount feature gate is enabled, \"MountOption\" is used.\nIf not specified and SELinuxMount feature gate is disabled, \"MountOption\" is used for ReadWriteOncePod volumes\nand \"Recursive\" for all other volumes.\n\nThis field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers.\n\nAll Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state.\nNote that this field cannot be set when spec.os.name is windows.",
"type": "string"
},
"seLinuxOptions": {
"description": "The SELinux context to be applied to all containers.\nIf unspecified, the container runtime will allocate a random SELinux context for each\ncontainer. May also be set in SecurityContext. If set in\nboth SecurityContext and PodSecurityContext, the value specified in SecurityContext\ntakes precedence for that container.\nNote that this field cannot be set when spec.os.name is windows.",
"properties": {
@@ -5328,10 +5332,11 @@
"type": "string"
},
"status": {
"description": "Status is the status of the condition.\nCan be True, False, Unknown.\nMore 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",
"type": "string"
},
"type": {
"description": "PersistentVolumeClaimConditionType defines the condition of PV claim.\nValid values are:\n - \"Resizing\", \"FileSystemResizePending\"\n\nIf RecoverVolumeExpansionFailure feature gate is enabled, then following additional values can be expected:\n - \"ControllerResizeError\", \"NodeResizeError\"\n\nIf VolumeAttributesClass feature gate is enabled, then following additional values can be expected:\n - \"ModifyVolumeError\", \"ModifyingVolume\"",
"description": "Type is the type of the condition.\nMore 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"
}
},
@@ -5562,7 +5567,7 @@
"description": "Volume represents a named volume in a pod that may be accessed by any container in the pod.",
"properties": {
"awsElasticBlockStore": {
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree\nawsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
@@ -5588,7 +5593,7 @@
"type": "object"
},
"azureDisk": {
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.",
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\nDeprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type\nare redirected to the disk.csi.azure.com CSI driver.",
"properties": {
"cachingMode": {
"description": "cachingMode is the Host Caching mode: None, Read Only, Read Write.",
@@ -5624,7 +5629,7 @@
"type": "object"
},
"azureFile": {
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.",
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.\nDeprecated: AzureFile is deprecated. All operations for the in-tree azureFile type\nare redirected to the file.csi.azure.com CSI driver.",
"properties": {
"readOnly": {
"description": "readOnly defaults to false (read/write). ReadOnly here will force\nthe ReadOnly setting in VolumeMounts.",
@@ -5646,7 +5651,7 @@
"type": "object"
},
"cephfs": {
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime",
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime.\nDeprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.",
"properties": {
"monitors": {
"description": "monitors is Required: Monitors is a collection of Ceph monitors\nMore info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it",
@@ -5691,7 +5696,7 @@
"type": "object"
},
"cinder": {
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nDeprecated: Cinder is deprecated. All operations for the in-tree cinder type\nare redirected to the cinder.csi.openstack.org CSI driver.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
@@ -5773,7 +5778,7 @@
"x-kubernetes-map-type": "atomic"
},
"csi": {
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).",
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers.",
"properties": {
"driver": {
"description": "driver is the name of the CSI driver that handles this volume.\nConsult with your admin for the correct name as registered in the cluster.",
@@ -6135,7 +6140,7 @@
"type": "object"
},
"flexVolume": {
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.",
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.\nDeprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.",
"properties": {
"driver": {
"description": "driver is the name of the driver to use for this volume.",
@@ -6175,7 +6180,7 @@
"type": "object"
},
"flocker": {
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running",
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running.\nDeprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.",
"properties": {
"datasetName": {
"description": "datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker\nshould be considered as deprecated",
@@ -6189,7 +6194,7 @@
"type": "object"
},
"gcePersistentDisk": {
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: GCEPersistentDisk is deprecated. All operations for the in-tree\ngcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"properties": {
"fsType": {
"description": "fsType is filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
@@ -6215,7 +6220,7 @@
"type": "object"
},
"gitRepo": {
"description": "gitRepo represents a git repository at a particular revision.\nDEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"description": "gitRepo represents a git repository at a particular revision.\nDeprecated: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"properties": {
"directory": {
"description": "directory is the target directory name.\nMust not contain or start with '..'. If '.' is supplied, the volume directory will be the\ngit repository. Otherwise, if specified, the volume will contain the git repository in\nthe subdirectory with the given name.",
@@ -6236,7 +6241,7 @@
"type": "object"
},
"glusterfs": {
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nDeprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"properties": {
"endpoints": {
"description": "endpoints is the endpoint name that details Glusterfs topology.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod",
@@ -6401,7 +6406,7 @@
"type": "object"
},
"photonPersistentDisk": {
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine",
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine.\nDeprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -6418,7 +6423,7 @@
"type": "object"
},
"portworxVolume": {
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine",
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine.\nDeprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type\nare redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate\nis on.",
"properties": {
"fsType": {
"description": "fSType represents the filesystem type to mount\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -6719,7 +6724,7 @@
"type": "object"
},
"quobyte": {
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime",
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime.\nDeprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.",
"properties": {
"group": {
"description": "group to map volume access to\nDefault is no group",
@@ -6753,7 +6758,7 @@
"type": "object"
},
"rbd": {
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nDeprecated: RBD is deprecated and the in-tree rbd type is no longer supported.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#rbd",
@@ -6810,7 +6815,7 @@
"type": "object"
},
"scaleIO": {
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.",
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\nDeprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.",
"properties": {
"fsType": {
"default": "xfs",
@@ -6918,7 +6923,7 @@
"type": "object"
},
"storageos": {
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.",
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\nDeprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -6952,7 +6957,7 @@
"type": "object"
},
"vsphereVolume": {
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine",
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine.\nDeprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type\nare redirected to the csi.vsphere.vmware.com CSI driver.",
"properties": {
"fsType": {
"description": "fsType is filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",

123
jsonnet/prometheus-operator/prometheusagents-crd.json
View File

@@ -1403,7 +1403,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1417,7 +1417,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1473,7 +1473,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -1487,7 +1487,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1518,7 +1518,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1532,7 +1532,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1588,7 +1588,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -1602,7 +1602,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1636,7 +1636,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1655,7 +1655,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -1674,7 +1674,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1745,7 +1745,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1831,7 +1831,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1850,7 +1850,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -1869,7 +1869,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1940,7 +1940,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2209,7 +2209,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2228,7 +2228,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2247,7 +2247,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2318,7 +2318,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2904,7 +2904,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2918,7 +2918,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2974,7 +2974,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2988,7 +2988,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3019,7 +3019,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3033,7 +3033,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3089,7 +3089,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -3103,7 +3103,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3137,7 +3137,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3156,7 +3156,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3175,7 +3175,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3246,7 +3246,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3332,7 +3332,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3351,7 +3351,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3370,7 +3370,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3441,7 +3441,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3710,7 +3710,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3729,7 +3729,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3748,7 +3748,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3819,7 +3819,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -5952,6 +5952,10 @@
"format": "int64",
"type": "integer"
},
"seLinuxChangePolicy": {
"description": "seLinuxChangePolicy defines how the container's SELinux label is applied to all volumes used by the Pod.\nIt has no effect on nodes that do not support SELinux or to volumes does not support SELinux.\nValid values are \"MountOption\" and \"Recursive\".\n\n\"Recursive\" means relabeling of all files on all Pod volumes by the container runtime.\nThis may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node.\n\n\"MountOption\" mounts all eligible Pod volumes with `-o context` mount option.\nThis requires all Pods that share the same volume to use the same SELinux label.\nIt is not possible to share the same volume among privileged and unprivileged Pods.\nEligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes\nwhose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their\nCSIDriver instance. Other volumes are always re-labelled recursively.\n\"MountOption\" value is allowed only when SELinuxMount feature gate is enabled.\n\nIf not specified and SELinuxMount feature gate is enabled, \"MountOption\" is used.\nIf not specified and SELinuxMount feature gate is disabled, \"MountOption\" is used for ReadWriteOncePod volumes\nand \"Recursive\" for all other volumes.\n\nThis field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers.\n\nAll Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state.\nNote that this field cannot be set when spec.os.name is windows.",
"type": "string"
},
"seLinuxOptions": {
"description": "The SELinux context to be applied to all containers.\nIf unspecified, the container runtime will allocate a random SELinux context for each\ncontainer. May also be set in SecurityContext. If set in\nboth SecurityContext and PodSecurityContext, the value specified in SecurityContext\ntakes precedence for that container.\nNote that this field cannot be set when spec.os.name is windows.",
"properties": {
@@ -6643,10 +6647,11 @@
"type": "string"
},
"status": {
"description": "Status is the status of the condition.\nCan be True, False, Unknown.\nMore 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",
"type": "string"
},
"type": {
"description": "PersistentVolumeClaimConditionType defines the condition of PV claim.\nValid values are:\n - \"Resizing\", \"FileSystemResizePending\"\n\nIf RecoverVolumeExpansionFailure feature gate is enabled, then following additional values can be expected:\n - \"ControllerResizeError\", \"NodeResizeError\"\n\nIf VolumeAttributesClass feature gate is enabled, then following additional values can be expected:\n - \"ModifyVolumeError\", \"ModifyingVolume\"",
"description": "Type is the type of the condition.\nMore 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"
}
},
@@ -7127,7 +7132,7 @@
"description": "Volume represents a named volume in a pod that may be accessed by any container in the pod.",
"properties": {
"awsElasticBlockStore": {
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree\nawsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
@@ -7153,7 +7158,7 @@
"type": "object"
},
"azureDisk": {
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.",
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\nDeprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type\nare redirected to the disk.csi.azure.com CSI driver.",
"properties": {
"cachingMode": {
"description": "cachingMode is the Host Caching mode: None, Read Only, Read Write.",
@@ -7189,7 +7194,7 @@
"type": "object"
},
"azureFile": {
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.",
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.\nDeprecated: AzureFile is deprecated. All operations for the in-tree azureFile type\nare redirected to the file.csi.azure.com CSI driver.",
"properties": {
"readOnly": {
"description": "readOnly defaults to false (read/write). ReadOnly here will force\nthe ReadOnly setting in VolumeMounts.",
@@ -7211,7 +7216,7 @@
"type": "object"
},
"cephfs": {
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime",
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime.\nDeprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.",
"properties": {
"monitors": {
"description": "monitors is Required: Monitors is a collection of Ceph monitors\nMore info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it",
@@ -7256,7 +7261,7 @@
"type": "object"
},
"cinder": {
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nDeprecated: Cinder is deprecated. All operations for the in-tree cinder type\nare redirected to the cinder.csi.openstack.org CSI driver.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
@@ -7338,7 +7343,7 @@
"x-kubernetes-map-type": "atomic"
},
"csi": {
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).",
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers.",
"properties": {
"driver": {
"description": "driver is the name of the CSI driver that handles this volume.\nConsult with your admin for the correct name as registered in the cluster.",
@@ -7700,7 +7705,7 @@
"type": "object"
},
"flexVolume": {
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.",
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.\nDeprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.",
"properties": {
"driver": {
"description": "driver is the name of the driver to use for this volume.",
@@ -7740,7 +7745,7 @@
"type": "object"
},
"flocker": {
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running",
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running.\nDeprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.",
"properties": {
"datasetName": {
"description": "datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker\nshould be considered as deprecated",
@@ -7754,7 +7759,7 @@
"type": "object"
},
"gcePersistentDisk": {
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: GCEPersistentDisk is deprecated. All operations for the in-tree\ngcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"properties": {
"fsType": {
"description": "fsType is filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
@@ -7780,7 +7785,7 @@
"type": "object"
},
"gitRepo": {
"description": "gitRepo represents a git repository at a particular revision.\nDEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"description": "gitRepo represents a git repository at a particular revision.\nDeprecated: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"properties": {
"directory": {
"description": "directory is the target directory name.\nMust not contain or start with '..'. If '.' is supplied, the volume directory will be the\ngit repository. Otherwise, if specified, the volume will contain the git repository in\nthe subdirectory with the given name.",
@@ -7801,7 +7806,7 @@
"type": "object"
},
"glusterfs": {
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nDeprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"properties": {
"endpoints": {
"description": "endpoints is the endpoint name that details Glusterfs topology.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod",
@@ -7966,7 +7971,7 @@
"type": "object"
},
"photonPersistentDisk": {
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine",
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine.\nDeprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -7983,7 +7988,7 @@
"type": "object"
},
"portworxVolume": {
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine",
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine.\nDeprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type\nare redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate\nis on.",
"properties": {
"fsType": {
"description": "fSType represents the filesystem type to mount\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -8284,7 +8289,7 @@
"type": "object"
},
"quobyte": {
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime",
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime.\nDeprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.",
"properties": {
"group": {
"description": "group to map volume access to\nDefault is no group",
@@ -8318,7 +8323,7 @@
"type": "object"
},
"rbd": {
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nDeprecated: RBD is deprecated and the in-tree rbd type is no longer supported.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#rbd",
@@ -8375,7 +8380,7 @@
"type": "object"
},
"scaleIO": {
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.",
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\nDeprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.",
"properties": {
"fsType": {
"default": "xfs",
@@ -8483,7 +8488,7 @@
"type": "object"
},
"storageos": {
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.",
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\nDeprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -8517,7 +8522,7 @@
"type": "object"
},
"vsphereVolume": {
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine",
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine.\nDeprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type\nare redirected to the csi.vsphere.vmware.com CSI driver.",
"properties": {
"fsType": {
"description": "fsType is filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",

123
jsonnet/prometheus-operator/prometheuses-crd.json
View File

@@ -1993,7 +1993,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2007,7 +2007,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2063,7 +2063,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2077,7 +2077,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2108,7 +2108,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2122,7 +2122,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2178,7 +2178,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2192,7 +2192,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2226,7 +2226,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2245,7 +2245,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2264,7 +2264,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2335,7 +2335,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2421,7 +2421,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2440,7 +2440,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2459,7 +2459,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2530,7 +2530,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2799,7 +2799,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2818,7 +2818,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -2837,7 +2837,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2908,7 +2908,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3519,7 +3519,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3533,7 +3533,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3589,7 +3589,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -3603,7 +3603,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3634,7 +3634,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3648,7 +3648,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3704,7 +3704,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -3718,7 +3718,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3752,7 +3752,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3771,7 +3771,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3790,7 +3790,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3861,7 +3861,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3947,7 +3947,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3966,7 +3966,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3985,7 +3985,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -4056,7 +4056,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -4325,7 +4325,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -4344,7 +4344,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -4363,7 +4363,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -4434,7 +4434,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -7416,6 +7416,10 @@
"format": "int64",
"type": "integer"
},
"seLinuxChangePolicy": {
"description": "seLinuxChangePolicy defines how the container's SELinux label is applied to all volumes used by the Pod.\nIt has no effect on nodes that do not support SELinux or to volumes does not support SELinux.\nValid values are \"MountOption\" and \"Recursive\".\n\n\"Recursive\" means relabeling of all files on all Pod volumes by the container runtime.\nThis may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node.\n\n\"MountOption\" mounts all eligible Pod volumes with `-o context` mount option.\nThis requires all Pods that share the same volume to use the same SELinux label.\nIt is not possible to share the same volume among privileged and unprivileged Pods.\nEligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes\nwhose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their\nCSIDriver instance. Other volumes are always re-labelled recursively.\n\"MountOption\" value is allowed only when SELinuxMount feature gate is enabled.\n\nIf not specified and SELinuxMount feature gate is enabled, \"MountOption\" is used.\nIf not specified and SELinuxMount feature gate is disabled, \"MountOption\" is used for ReadWriteOncePod volumes\nand \"Recursive\" for all other volumes.\n\nThis field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers.\n\nAll Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state.\nNote that this field cannot be set when spec.os.name is windows.",
"type": "string"
},
"seLinuxOptions": {
"description": "The SELinux context to be applied to all containers.\nIf unspecified, the container runtime will allocate a random SELinux context for each\ncontainer. May also be set in SecurityContext. If set in\nboth SecurityContext and PodSecurityContext, the value specified in SecurityContext\ntakes precedence for that container.\nNote that this field cannot be set when spec.os.name is windows.",
"properties": {
@@ -8111,10 +8115,11 @@
"type": "string"
},
"status": {
"description": "Status is the status of the condition.\nCan be True, False, Unknown.\nMore 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",
"type": "string"
},
"type": {
"description": "PersistentVolumeClaimConditionType defines the condition of PV claim.\nValid values are:\n - \"Resizing\", \"FileSystemResizePending\"\n\nIf RecoverVolumeExpansionFailure feature gate is enabled, then following additional values can be expected:\n - \"ControllerResizeError\", \"NodeResizeError\"\n\nIf VolumeAttributesClass feature gate is enabled, then following additional values can be expected:\n - \"ModifyVolumeError\", \"ModifyingVolume\"",
"description": "Type is the type of the condition.\nMore 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"
}
},
@@ -9036,7 +9041,7 @@
"description": "Volume represents a named volume in a pod that may be accessed by any container in the pod.",
"properties": {
"awsElasticBlockStore": {
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree\nawsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
@@ -9062,7 +9067,7 @@
"type": "object"
},
"azureDisk": {
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.",
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\nDeprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type\nare redirected to the disk.csi.azure.com CSI driver.",
"properties": {
"cachingMode": {
"description": "cachingMode is the Host Caching mode: None, Read Only, Read Write.",
@@ -9098,7 +9103,7 @@
"type": "object"
},
"azureFile": {
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.",
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.\nDeprecated: AzureFile is deprecated. All operations for the in-tree azureFile type\nare redirected to the file.csi.azure.com CSI driver.",
"properties": {
"readOnly": {
"description": "readOnly defaults to false (read/write). ReadOnly here will force\nthe ReadOnly setting in VolumeMounts.",
@@ -9120,7 +9125,7 @@
"type": "object"
},
"cephfs": {
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime",
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime.\nDeprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.",
"properties": {
"monitors": {
"description": "monitors is Required: Monitors is a collection of Ceph monitors\nMore info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it",
@@ -9165,7 +9170,7 @@
"type": "object"
},
"cinder": {
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nDeprecated: Cinder is deprecated. All operations for the in-tree cinder type\nare redirected to the cinder.csi.openstack.org CSI driver.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
@@ -9247,7 +9252,7 @@
"x-kubernetes-map-type": "atomic"
},
"csi": {
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).",
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers.",
"properties": {
"driver": {
"description": "driver is the name of the CSI driver that handles this volume.\nConsult with your admin for the correct name as registered in the cluster.",
@@ -9609,7 +9614,7 @@
"type": "object"
},
"flexVolume": {
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.",
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.\nDeprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.",
"properties": {
"driver": {
"description": "driver is the name of the driver to use for this volume.",
@@ -9649,7 +9654,7 @@
"type": "object"
},
"flocker": {
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running",
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running.\nDeprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.",
"properties": {
"datasetName": {
"description": "datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker\nshould be considered as deprecated",
@@ -9663,7 +9668,7 @@
"type": "object"
},
"gcePersistentDisk": {
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: GCEPersistentDisk is deprecated. All operations for the in-tree\ngcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"properties": {
"fsType": {
"description": "fsType is filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
@@ -9689,7 +9694,7 @@
"type": "object"
},
"gitRepo": {
"description": "gitRepo represents a git repository at a particular revision.\nDEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"description": "gitRepo represents a git repository at a particular revision.\nDeprecated: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"properties": {
"directory": {
"description": "directory is the target directory name.\nMust not contain or start with '..'. If '.' is supplied, the volume directory will be the\ngit repository. Otherwise, if specified, the volume will contain the git repository in\nthe subdirectory with the given name.",
@@ -9710,7 +9715,7 @@
"type": "object"
},
"glusterfs": {
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nDeprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"properties": {
"endpoints": {
"description": "endpoints is the endpoint name that details Glusterfs topology.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod",
@@ -9875,7 +9880,7 @@
"type": "object"
},
"photonPersistentDisk": {
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine",
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine.\nDeprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -9892,7 +9897,7 @@
"type": "object"
},
"portworxVolume": {
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine",
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine.\nDeprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type\nare redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate\nis on.",
"properties": {
"fsType": {
"description": "fSType represents the filesystem type to mount\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -10193,7 +10198,7 @@
"type": "object"
},
"quobyte": {
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime",
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime.\nDeprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.",
"properties": {
"group": {
"description": "group to map volume access to\nDefault is no group",
@@ -10227,7 +10232,7 @@
"type": "object"
},
"rbd": {
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nDeprecated: RBD is deprecated and the in-tree rbd type is no longer supported.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#rbd",
@@ -10284,7 +10289,7 @@
"type": "object"
},
"scaleIO": {
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.",
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\nDeprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.",
"properties": {
"fsType": {
"default": "xfs",
@@ -10392,7 +10397,7 @@
"type": "object"
},
"storageos": {
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.",
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\nDeprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -10426,7 +10431,7 @@
"type": "object"
},
"vsphereVolume": {
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine",
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine.\nDeprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type\nare redirected to the csi.vsphere.vmware.com CSI driver.",
"properties": {
"fsType": {
"description": "fsType is filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",

123
jsonnet/prometheus-operator/thanosrulers-crd.json
View File

@@ -1140,7 +1140,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1154,7 +1154,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1210,7 +1210,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -1224,7 +1224,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1255,7 +1255,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1269,7 +1269,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1325,7 +1325,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -1339,7 +1339,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1373,7 +1373,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1392,7 +1392,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -1411,7 +1411,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1482,7 +1482,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1568,7 +1568,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1587,7 +1587,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -1606,7 +1606,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -1677,7 +1677,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -1946,7 +1946,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -1965,7 +1965,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -1984,7 +1984,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2055,7 +2055,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2753,7 +2753,7 @@
"description": "PostStart is called immediately after a container is created. If the handler fails,\nthe container is terminated and restarted according to its restart policy.\nOther management of the container blocks until the hook completes.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2767,7 +2767,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2823,7 +2823,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2837,7 +2837,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2868,7 +2868,7 @@
"description": "PreStop is called immediately before a container is terminated due to an\nAPI request or management event such as liveness/startup probe failure,\npreemption, resource contention, etc. The handler is not called if the\ncontainer crashes or exits. The Pod's termination grace period countdown begins before the\nPreStop hook is executed. Regardless of the outcome of the handler, the\ncontainer will eventually terminate within the Pod's termination grace\nperiod (unless delayed by finalizers). Other management of the container blocks until the hook completes\nor until the termination grace period is reached.\nMore info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -2882,7 +2882,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -2938,7 +2938,7 @@
"type": "object"
},
"sleep": {
"description": "Sleep represents the duration that the container should sleep before being terminated.",
"description": "Sleep represents a duration that the container should sleep.",
"properties": {
"seconds": {
"description": "Seconds is the number of seconds to sleep.",
@@ -2952,7 +2952,7 @@
"type": "object"
},
"tcpSocket": {
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor the backward compatibility. There are no validation of this field and\nlifecycle hooks will fail in runtime when tcp handler is specified.",
"description": "Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept\nfor backward compatibility. There is no validation of this field and\nlifecycle hooks will fail at runtime when it is specified.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -2986,7 +2986,7 @@
"description": "Periodic probe of container liveness.\nContainer will be restarted if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3005,7 +3005,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3024,7 +3024,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3095,7 +3095,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3181,7 +3181,7 @@
"description": "Periodic probe of container service readiness.\nContainer will be removed from service endpoints if the probe fails.\nCannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3200,7 +3200,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3219,7 +3219,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3290,7 +3290,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -3559,7 +3559,7 @@
"description": "StartupProbe indicates that the Pod has successfully initialized.\nIf specified, no other probes are executed until this completes successfully.\nIf this probe fails, the Pod will be restarted, just as if the livenessProbe failed.\nThis can be used to provide different probe parameters at the beginning of a Pod's lifecycle,\nwhen it might take a long time to load data or warm a cache, than during steady-state operation.\nThis cannot be updated.\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes",
"properties": {
"exec": {
"description": "Exec specifies the action to take.",
"description": "Exec specifies a command to execute in the container.",
"properties": {
"command": {
"description": "Command is the command line to execute inside the container, the working directory for the\ncommand is root ('/') in the container's filesystem. The command is simply exec'd, it is\nnot run inside a shell, so traditional shell instructions ('|', etc) won't work. To use\na shell, you need to explicitly call out to that shell.\nExit status of 0 is treated as live/healthy and non-zero is unhealthy.",
@@ -3578,7 +3578,7 @@
"type": "integer"
},
"grpc": {
"description": "GRPC specifies an action involving a GRPC port.",
"description": "GRPC specifies a GRPC HealthCheckRequest.",
"properties": {
"port": {
"description": "Port number of the gRPC service. Number must be in the range 1 to 65535.",
@@ -3597,7 +3597,7 @@
"type": "object"
},
"httpGet": {
"description": "HTTPGet specifies the http request to perform.",
"description": "HTTPGet specifies an HTTP GET request to perform.",
"properties": {
"host": {
"description": "Host name to connect to, defaults to the pod IP. You probably want to set\n\"Host\" in httpHeaders instead.",
@@ -3668,7 +3668,7 @@
"type": "integer"
},
"tcpSocket": {
"description": "TCPSocket specifies an action involving a TCP port.",
"description": "TCPSocket specifies a connection to a TCP port.",
"properties": {
"host": {
"description": "Optional: Host name to connect to, defaults to the pod IP.",
@@ -4179,6 +4179,10 @@
"format": "int64",
"type": "integer"
},
"seLinuxChangePolicy": {
"description": "seLinuxChangePolicy defines how the container's SELinux label is applied to all volumes used by the Pod.\nIt has no effect on nodes that do not support SELinux or to volumes does not support SELinux.\nValid values are \"MountOption\" and \"Recursive\".\n\n\"Recursive\" means relabeling of all files on all Pod volumes by the container runtime.\nThis may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node.\n\n\"MountOption\" mounts all eligible Pod volumes with `-o context` mount option.\nThis requires all Pods that share the same volume to use the same SELinux label.\nIt is not possible to share the same volume among privileged and unprivileged Pods.\nEligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes\nwhose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their\nCSIDriver instance. Other volumes are always re-labelled recursively.\n\"MountOption\" value is allowed only when SELinuxMount feature gate is enabled.\n\nIf not specified and SELinuxMount feature gate is enabled, \"MountOption\" is used.\nIf not specified and SELinuxMount feature gate is disabled, \"MountOption\" is used for ReadWriteOncePod volumes\nand \"Recursive\" for all other volumes.\n\nThis field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers.\n\nAll Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state.\nNote that this field cannot be set when spec.os.name is windows.",
"type": "string"
},
"seLinuxOptions": {
"description": "The SELinux context to be applied to all containers.\nIf unspecified, the container runtime will allocate a random SELinux context for each\ncontainer. May also be set in SecurityContext. If set in\nboth SecurityContext and PodSecurityContext, the value specified in SecurityContext\ntakes precedence for that container.\nNote that this field cannot be set when spec.os.name is windows.",
"properties": {
@@ -4767,10 +4771,11 @@
"type": "string"
},
"status": {
"description": "Status is the status of the condition.\nCan be True, False, Unknown.\nMore 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",
"type": "string"
},
"type": {
"description": "PersistentVolumeClaimConditionType defines the condition of PV claim.\nValid values are:\n - \"Resizing\", \"FileSystemResizePending\"\n\nIf RecoverVolumeExpansionFailure feature gate is enabled, then following additional values can be expected:\n - \"ControllerResizeError\", \"NodeResizeError\"\n\nIf VolumeAttributesClass feature gate is enabled, then following additional values can be expected:\n - \"ModifyVolumeError\", \"ModifyingVolume\"",
"description": "Type is the type of the condition.\nMore 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"
}
},
@@ -5024,7 +5029,7 @@
"description": "Volume represents a named volume in a pod that may be accessed by any container in the pod.",
"properties": {
"awsElasticBlockStore": {
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"description": "awsElasticBlockStore represents an AWS Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree\nawsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore",
@@ -5050,7 +5055,7 @@
"type": "object"
},
"azureDisk": {
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.",
"description": "azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.\nDeprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type\nare redirected to the disk.csi.azure.com CSI driver.",
"properties": {
"cachingMode": {
"description": "cachingMode is the Host Caching mode: None, Read Only, Read Write.",
@@ -5086,7 +5091,7 @@
"type": "object"
},
"azureFile": {
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.",
"description": "azureFile represents an Azure File Service mount on the host and bind mount to the pod.\nDeprecated: AzureFile is deprecated. All operations for the in-tree azureFile type\nare redirected to the file.csi.azure.com CSI driver.",
"properties": {
"readOnly": {
"description": "readOnly defaults to false (read/write). ReadOnly here will force\nthe ReadOnly setting in VolumeMounts.",
@@ -5108,7 +5113,7 @@
"type": "object"
},
"cephfs": {
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime",
"description": "cephFS represents a Ceph FS mount on the host that shares a pod's lifetime.\nDeprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.",
"properties": {
"monitors": {
"description": "monitors is Required: Monitors is a collection of Ceph monitors\nMore info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it",
@@ -5153,7 +5158,7 @@
"type": "object"
},
"cinder": {
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"description": "cinder represents a cinder volume attached and mounted on kubelets host machine.\nDeprecated: Cinder is deprecated. All operations for the in-tree cinder type\nare redirected to the cinder.csi.openstack.org CSI driver.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://examples.k8s.io/mysql-cinder-pd/README.md",
@@ -5235,7 +5240,7 @@
"x-kubernetes-map-type": "atomic"
},
"csi": {
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature).",
"description": "csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers.",
"properties": {
"driver": {
"description": "driver is the name of the CSI driver that handles this volume.\nConsult with your admin for the correct name as registered in the cluster.",
@@ -5597,7 +5602,7 @@
"type": "object"
},
"flexVolume": {
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.",
"description": "flexVolume represents a generic volume resource that is\nprovisioned/attached using an exec based plugin.\nDeprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.",
"properties": {
"driver": {
"description": "driver is the name of the driver to use for this volume.",
@@ -5637,7 +5642,7 @@
"type": "object"
},
"flocker": {
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running",
"description": "flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running.\nDeprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.",
"properties": {
"datasetName": {
"description": "datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker\nshould be considered as deprecated",
@@ -5651,7 +5656,7 @@
"type": "object"
},
"gcePersistentDisk": {
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"description": "gcePersistentDisk represents a GCE Disk resource that is attached to a\nkubelet's host machine and then exposed to the pod.\nDeprecated: GCEPersistentDisk is deprecated. All operations for the in-tree\ngcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
"properties": {
"fsType": {
"description": "fsType is filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk",
@@ -5677,7 +5682,7 @@
"type": "object"
},
"gitRepo": {
"description": "gitRepo represents a git repository at a particular revision.\nDEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"description": "gitRepo represents a git repository at a particular revision.\nDeprecated: GitRepo is deprecated. To provision a container with a git repo, mount an\nEmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir\ninto the Pod's container.",
"properties": {
"directory": {
"description": "directory is the target directory name.\nMust not contain or start with '..'. If '.' is supplied, the volume directory will be the\ngit repository. Otherwise, if specified, the volume will contain the git repository in\nthe subdirectory with the given name.",
@@ -5698,7 +5703,7 @@
"type": "object"
},
"glusterfs": {
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"description": "glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime.\nDeprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md",
"properties": {
"endpoints": {
"description": "endpoints is the endpoint name that details Glusterfs topology.\nMore info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod",
@@ -5863,7 +5868,7 @@
"type": "object"
},
"photonPersistentDisk": {
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine",
"description": "photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine.\nDeprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -5880,7 +5885,7 @@
"type": "object"
},
"portworxVolume": {
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine",
"description": "portworxVolume represents a portworx volume attached and mounted on kubelets host machine.\nDeprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type\nare redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate\nis on.",
"properties": {
"fsType": {
"description": "fSType represents the filesystem type to mount\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -6181,7 +6186,7 @@
"type": "object"
},
"quobyte": {
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime",
"description": "quobyte represents a Quobyte mount on the host that shares a pod's lifetime.\nDeprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.",
"properties": {
"group": {
"description": "group to map volume access to\nDefault is no group",
@@ -6215,7 +6220,7 @@
"type": "object"
},
"rbd": {
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"description": "rbd represents a Rados Block Device mount on the host that shares a pod's lifetime.\nDeprecated: RBD is deprecated and the in-tree rbd type is no longer supported.\nMore info: https://examples.k8s.io/volumes/rbd/README.md",
"properties": {
"fsType": {
"description": "fsType is the filesystem type of the volume that you want to mount.\nTip: Ensure that the filesystem type is supported by the host operating system.\nExamples: \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.\nMore info: https://kubernetes.io/docs/concepts/storage/volumes#rbd",
@@ -6272,7 +6277,7 @@
"type": "object"
},
"scaleIO": {
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.",
"description": "scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.\nDeprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.",
"properties": {
"fsType": {
"default": "xfs",
@@ -6380,7 +6385,7 @@
"type": "object"
},
"storageos": {
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.",
"description": "storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.\nDeprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported.",
"properties": {
"fsType": {
"description": "fsType is the filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
@@ -6414,7 +6419,7 @@
"type": "object"
},
"vsphereVolume": {
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine",
"description": "vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine.\nDeprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type\nare redirected to the csi.vsphere.vmware.com CSI driver.",
"properties": {
"fsType": {
"description": "fsType is filesystem type to mount.\nMust be a filesystem type supported by the host operating system.\nEx. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",