spec.monitoring.enableMetrics | If this flag is enabled it will expose the storage cluster metrics to external monitoring solutions like Prometheus. DEPRECATED - use prometheus.exportMetrics instead | boolean |
spec.monitoring.prometheus | Contains configuration of Prometheus to monitor the storage cluster. | object |
spec.monitoring.prometheus.resources | Define resources requests and limits for single Pods. | object |
spec.monitoring.prometheus.resources.limits | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ | object |
spec.monitoring.prometheus.resources.requests | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ | object |
spec.monitoring.prometheus.securityContext | Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ | object |
spec.monitoring.prometheus.securityContext.allowPrivilegeEscalation | AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN | boolean |
spec.monitoring.prometheus.securityContext.capabilities | The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime. | object |
spec.monitoring.prometheus.securityContext.capabilities.add | Added capabilities | array |
spec.monitoring.prometheus.securityContext.capabilities.drop | Removed capabilities | array |
spec.monitoring.prometheus.securityContext.privileged | Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. | boolean |
spec.monitoring.prometheus.securityContext.procMount | procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. | string |
spec.monitoring.prometheus.securityContext.readOnlyRootFilesystem | Whether this container has a read-only root filesystem. Default is false. | boolean |
spec.monitoring.prometheus.securityContext.runAsGroup | The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | integer |
spec.monitoring.prometheus.securityContext.runAsNonRoot | Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | boolean |
spec.monitoring.prometheus.securityContext.runAsUser | The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | integer |
spec.monitoring.prometheus.securityContext.seLinuxOptions | The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | object |
spec.monitoring.prometheus.securityContext.seLinuxOptions.level | Level is SELinux level label that applies to the container. | string |
spec.monitoring.prometheus.securityContext.seLinuxOptions.role | Role is a SELinux role label that applies to the container. | string |
spec.monitoring.prometheus.securityContext.seLinuxOptions.type | Type is a SELinux type label that applies to the container. | string |
spec.monitoring.prometheus.securityContext.seLinuxOptions.user | User is a SELinux user label that applies to the container. | string |
spec.monitoring.prometheus.securityContext.windowsOptions | The Windows specific settings applied to all containers. If unspecified, the options from the PodSecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | object |
spec.monitoring.prometheus.securityContext.windowsOptions.gmsaCredentialSpec | GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. | string |
spec.monitoring.prometheus.securityContext.windowsOptions.gmsaCredentialSpecName | GMSACredentialSpecName is the name of the GMSA credential spec to use. | string |
spec.monitoring.prometheus.securityContext.windowsOptions.runAsUserName | The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. | string |
spec.monitoring.prometheus.exportMetrics | If this flag is enabled it will expose the storage cluster metrics to Prometheus. | boolean |
spec.monitoring.prometheus.enabled | Flag indicating whether Prometheus stack needs to be enabled and deployed by the Storage operator. | boolean |
spec.monitoring.prometheus.remoteWriteEndpoint | Specifies the remote write endpoint for Prometheus. | string |
spec.monitoring.prometheus.alertManager | Contains configuration of AlertManager for the storage cluster. | object |
spec.monitoring.prometheus.alertManager.enabled | Flag indicating whether AlertManager needs to be enabled and deployed by the Storage operator. | boolean |
spec.monitoring.prometheus.replicas | Total number of non-terminated pods targeted by this Prometheus deployment (their labels match the selector). | integer |
spec.monitoring.prometheus.retention | Time duration Prometheus shall retain data for. Default is '24h' if retentionSize is not set, and must match the regular expression `[0-9]+(ms | s |
spec.monitoring.prometheus.retentionSize | Maximum amount of disk space used by blocks. | string |
spec.monitoring.prometheus.storage | Storage spec to specify how storage shall be used. | object |
spec.monitoring.prometheus.storage.disableMountSubPath | Deprecated: subPath usage will be disabled by default in a future release, this option will become unnecessary. DisableMountSubPath allows to remove any subPath usage in volume mounts. | boolean |
spec.monitoring.prometheus.storage.emptyDir | EmptyDirVolumeSource to be used by the StatefulSet. If specified, used in place of any volumeClaimTemplate. More info: https://kubernetes.io/docs/concepts/storage/volumes/#emptydir | object |
spec.monitoring.prometheus.storage.emptyDir.medium | medium represents what type of storage medium should back this directory. The default is "" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir | string |
spec.monitoring.prometheus.storage.ephemeral | EphemeralVolumeSource to be used by the StatefulSet. This is a beta field in k8s 1.21, for lower versions, starting with k8s 1.19, it requires enabling the GenericEphemeralVolume feature gate. More info: https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate | Will be used to create a stand-alone PVC to provision the volume. The pod in which this EphemeralVolumeSource is embedded will be the owner of the PVC, i.e. the PVC will be deleted together with the pod. The name of the PVC will be \<pod name>-\<volume name> where \<volume name> is the name from the PodSpec.Volumes array entry. Pod validation will reject the pod if the concatenated name is not valid for a PVC (for example, too long). An existing PVC with that name that is not owned by the pod will not be used for the pod to avoid using an unrelated volume by mistake. Starting the pod is then blocked until the unrelated PVC is removed. If such a pre-created PVC is meant to be used by the pod, the PVC has to updated with an owner reference to the pod once the pod exists. Normally this should not be necessary, but it may be useful when manually reconstructing a broken cluster. This field is read-only and no changes will be made by Kubernetes to the PVC after it has been created. Required, must not be nil. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.metadata | May contain labels and annotations that will be copied into the PVC when creating it. No other fields are allowed and will be rejected during validation. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec | The specification for the PersistentVolumeClaim. The entire content is copied unchanged into the PVC that gets created from this template. The same fields as in a PersistentVolumeClaim are also valid here. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.accessModes | accessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1 | array |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSource | dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSource.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSource.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSource.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSourceRef | dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects. * While dataSource ignores disallowed values (dropping them), dataSourceRef preserves all values, and generates an error if a disallowed value is specified. * While dataSource only allows local objects, dataSourceRef allows objects in any namespaces. (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSourceRef.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSourceRef.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSourceRef.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.dataSourceRef.namespace | Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace's owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.resources | resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.resources.claims | Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. | array |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.resources.claims.name | Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.resources.limits | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.resources.requests | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector | selector is a label query over volumes to consider for binding. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions | matchExpressions is a list of label selector requirements. The requirements are ANDed. | array |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.key | key is the label key that the selector applies to. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.operator | operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.values | values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch. | array |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.selector.matchLabels | matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed. | object |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.storageClassName | storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1 | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.volumeMode | volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec. | string |
spec.monitoring.prometheus.storage.ephemeral.volumeClaimTemplate.spec.volumeName | volumeName is the binding reference to the PersistentVolume backing this claim. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate | A PVC spec to be used by the StatefulSet. The easiest way to use a volume that cannot be automatically provisioned (for whatever reason) is to use a label selector alongside manually created PersistentVolumes. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.apiVersion | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.kind | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.metadata | EmbeddedMetadata contains metadata relevant to an EmbeddedResource. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.metadata.annotations | Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.metadata.labels | Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.metadata.name | Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec | Spec defines the desired characteristics of a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.accessModes | accessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1 | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSource | dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSource.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSource.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSource.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSourceRef | dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects. * While dataSource ignores disallowed values (dropping them), dataSourceRef preserves all values, and generates an error if a disallowed value is specified. * While dataSource only allows local objects, dataSourceRef allows objects in any namespaces. (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSourceRef.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSourceRef.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSourceRef.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.dataSourceRef.namespace | Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace's owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.resources | resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.resources.claims | Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.resources.claims.name | Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.resources.limits | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.resources.requests | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector | selector is a label query over volumes to consider for binding. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector.matchExpressions | matchExpressions is a list of label selector requirements. The requirements are ANDed. | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector.matchExpressions.key | key is the label key that the selector applies to. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector.matchExpressions.operator | operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector.matchExpressions.values | values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch. | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.selector.matchLabels | matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.storageClassName | storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1 | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.volumeMode | volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.spec.volumeName | volumeName is the binding reference to the PersistentVolume backing this claim. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status | Status represents the current information/status of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.accessModes | accessModes contains the actual access modes the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1 | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.allocatedResources | allocatedResources is the storage resource within AllocatedResources tracks the capacity allocated to a PVC. It may be larger than the actual capacity when a volume expansion operation is requested. For storage quota, the larger value from allocatedResources and PVC.spec.resources is used. If allocatedResources is not set, PVC.spec.resources alone is used for quota calculation. If a volume expansion capacity request is lowered, allocatedResources is only lowered if there are no expansion operations in progress and if the actual volume capacity is equal or lower than the requested capacity. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.capacity | capacity represents the actual resources of the underlying volume. | object |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions | conditions is the current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to 'ResizeStarted'. | array |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions.lastProbeTime | lastProbeTime is the time we probed the condition. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions.lastTransitionTime | lastTransitionTime is the time the condition transitioned from one status to another. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions.message | message is the human-readable message indicating details about last transition. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions.reason | reason is a unique, this should be a short, machine understandable string that gives the reason for condition's last transition. If it reports "ResizeStarted" that means the underlying persistent volume is being resized. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.conditions.type | PersistentVolumeClaimConditionType is a valid value of PersistentVolumeClaimCondition.Type | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.phase | phase represents the current phase of PersistentVolumeClaim. | string |
spec.monitoring.prometheus.storage.volumeClaimTemplate.status.resizeStatus | resizeStatus stores status of resize operation. ResizeStatus is not set by default but when expansion is complete resizeStatus is set to empty string by resize controller or kubelet. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature. | string |
spec.monitoring.prometheus.volumes | Volumes allows configuration of additional volumes on the output StatefulSet definition. Volumes specified will be appended to other volumes that are generated as a result of StorageSpec objects. | array |
spec.monitoring.prometheus.volumes.awsElasticBlockStore | awsElasticBlockStore represents an AWS Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore | object |
spec.monitoring.prometheus.volumes.awsElasticBlockStore.fsType | fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore TODO: how do we prevent errors in the filesystem from compromising the machine | string |
spec.monitoring.prometheus.volumes.awsElasticBlockStore.partition | partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). | integer |
spec.monitoring.prometheus.volumes.awsElasticBlockStore.readOnly | readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore | boolean |
spec.monitoring.prometheus.volumes.awsElasticBlockStore.volumeID | volumeID is unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore | string |
spec.monitoring.prometheus.volumes.azureDisk | azureDisk represents an Azure Data Disk mount on the host and bind mount to the pod. | object |
spec.monitoring.prometheus.volumes.azureDisk.cachingMode | cachingMode is the Host Caching mode: None, Read Only, Read Write. | string |
spec.monitoring.prometheus.volumes.azureDisk.diskName | diskName is the Name of the data disk in the blob storage | string |
spec.monitoring.prometheus.volumes.azureDisk.diskURI | diskURI is the URI of data disk in the blob storage | string |
spec.monitoring.prometheus.volumes.azureDisk.fsType | fsType is Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. | string |
spec.monitoring.prometheus.volumes.azureDisk.kind | kind expected values are Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared | string |
spec.monitoring.prometheus.volumes.azureDisk.readOnly | readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.azureFile | azureFile represents an Azure File Service mount on the host and bind mount to the pod. | object |
spec.monitoring.prometheus.volumes.azureFile.readOnly | readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.azureFile.secretName | secretName is the name of secret that contains Azure Storage Account Name and Key | string |
spec.monitoring.prometheus.volumes.azureFile.shareName | shareName is the azure share Name | string |
spec.monitoring.prometheus.volumes.cephfs | cephFS represents a Ceph FS mount on the host that shares a pod's lifetime | object |
spec.monitoring.prometheus.volumes.cephfs.monitors | monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it | array |
spec.monitoring.prometheus.volumes.cephfs.path | path is Optional: Used as the mounted root, rather than the full Ceph tree, default is / | string |
spec.monitoring.prometheus.volumes.cephfs.readOnly | readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it | boolean |
spec.monitoring.prometheus.volumes.cephfs.secretFile | secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.cephfs.secretRef | secretRef is Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it | object |
spec.monitoring.prometheus.volumes.cephfs.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.cephfs.user | user is optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.cinder | cinder represents a cinder volume attached and mounted on kubelets host machine. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | object |
spec.monitoring.prometheus.volumes.cinder.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | string |
spec.monitoring.prometheus.volumes.cinder.readOnly | readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | boolean |
spec.monitoring.prometheus.volumes.cinder.secretRef | secretRef is optional: points to a secret object containing parameters used to connect to OpenStack. | object |
spec.monitoring.prometheus.volumes.cinder.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.cinder.volumeID | volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | string |
spec.monitoring.prometheus.volumes.configMap | configMap represents a configMap that should populate this volume | object |
spec.monitoring.prometheus.volumes.configMap.defaultMode | defaultMode is optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.configMap.items | items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. | array |
spec.monitoring.prometheus.volumes.configMap.items.key | key is the key to project. | string |
spec.monitoring.prometheus.volumes.configMap.items.mode | mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.configMap.items.path | path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. | string |
spec.monitoring.prometheus.volumes.configMap.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.configMap.optional | optional specify whether the ConfigMap or its keys must be defined | boolean |
spec.monitoring.prometheus.volumes.csi | csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers (Beta feature). | object |
spec.monitoring.prometheus.volumes.csi.driver | driver is the name of the CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster. | string |
spec.monitoring.prometheus.volumes.csi.fsType | fsType to mount. Ex. "ext4", "xfs", "ntfs". If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply. | string |
spec.monitoring.prometheus.volumes.csi.nodePublishSecretRef | nodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secret references are passed. | object |
spec.monitoring.prometheus.volumes.csi.nodePublishSecretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.csi.readOnly | readOnly specifies a read-only configuration for the volume. Defaults to false (read/write). | boolean |
spec.monitoring.prometheus.volumes.csi.volumeAttributes | volumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver's documentation for supported values. | object |
spec.monitoring.prometheus.volumes.downwardAPI | downwardAPI represents downward API about the pod that should populate this volume | object |
spec.monitoring.prometheus.volumes.downwardAPI.defaultMode | Optional: mode bits to use on created files by default. Must be a Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.downwardAPI.items | Items is a list of downward API volume file | array |
spec.monitoring.prometheus.volumes.downwardAPI.items.fieldRef | Required: Selects a field of the pod: only annotations, labels, name and namespace are supported. | object |
spec.monitoring.prometheus.volumes.downwardAPI.items.fieldRef.apiVersion | Version of the schema the FieldPath is written in terms of, defaults to "v1". | string |
spec.monitoring.prometheus.volumes.downwardAPI.items.fieldRef.fieldPath | Path of the field to select in the specified API version. | string |
spec.monitoring.prometheus.volumes.downwardAPI.items.mode | Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.downwardAPI.items.path | Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..' | string |
spec.monitoring.prometheus.volumes.downwardAPI.items.resourceFieldRef | Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported. | object |
spec.monitoring.prometheus.volumes.downwardAPI.items.resourceFieldRef.containerName | Container name: required for volumes, optional for env vars | string |
spec.monitoring.prometheus.volumes.downwardAPI.items.resourceFieldRef.resource | Required: resource to select | string |
spec.monitoring.prometheus.volumes.emptyDir | emptyDir represents a temporary directory that shares a pod's lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir | object |
spec.monitoring.prometheus.volumes.emptyDir.medium | medium represents what type of storage medium should back this directory. The default is "" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir | string |
spec.monitoring.prometheus.volumes.ephemeral | ephemeral represents a volume that is handled by a cluster storage driver. The volume's lifecycle is tied to the pod that defines it - it will be created before the pod starts, and deleted when the pod is removed. Use this if: a) the volume is only needed while the pod runs, b) features of normal volumes like restoring from snapshot or capacity tracking are needed, c) the storage driver is specified through a storage class, and d) the storage driver supports dynamic volume provisioning through a PersistentVolumeClaim (see EphemeralVolumeSource for more information on the connection between this volume type and PersistentVolumeClaim). Use PersistentVolumeClaim or one of the vendor-specific APIs for volumes that persist for longer than the lifecycle of an individual pod. Use CSI for light-weight local ephemeral volumes if the CSI driver is meant to be used that way - see the documentation of the driver for more information. A pod can use both types of ephemeral volumes and persistent volumes at the same time. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate | Will be used to create a stand-alone PVC to provision the volume. The pod in which this EphemeralVolumeSource is embedded will be the owner of the PVC, i.e. the PVC will be deleted together with the pod. The name of the PVC will be \<pod name>-\<volume name> where \<volume name> is the name from the PodSpec.Volumes array entry. Pod validation will reject the pod if the concatenated name is not valid for a PVC (for example, too long). An existing PVC with that name that is not owned by the pod will not be used for the pod to avoid using an unrelated volume by mistake. Starting the pod is then blocked until the unrelated PVC is removed. If such a pre-created PVC is meant to be used by the pod, the PVC has to updated with an owner reference to the pod once the pod exists. Normally this should not be necessary, but it may be useful when manually reconstructing a broken cluster. This field is read-only and no changes will be made by Kubernetes to the PVC after it has been created. Required, must not be nil. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.metadata | May contain labels and annotations that will be copied into the PVC when creating it. No other fields are allowed and will be rejected during validation. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec | The specification for the PersistentVolumeClaim. The entire content is copied unchanged into the PVC that gets created from this template. The same fields as in a PersistentVolumeClaim are also valid here. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.accessModes | accessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1 | array |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSource | dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSource.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSource.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSource.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSourceRef | dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects. * While dataSource ignores disallowed values (dropping them), dataSourceRef preserves all values, and generates an error if a disallowed value is specified. * While dataSource only allows local objects, dataSourceRef allows objects in any namespaces. (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSourceRef.apiGroup | APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSourceRef.kind | Kind is the type of resource being referenced | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSourceRef.name | Name is the name of resource being referenced | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.dataSourceRef.namespace | Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace's owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.resources | resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.resources.claims | Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. | array |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.resources.claims.name | Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.resources.limits | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.resources.requests | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector | selector is a label query over volumes to consider for binding. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions | matchExpressions is a list of label selector requirements. The requirements are ANDed. | array |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.key | key is the label key that the selector applies to. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.operator | operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector.matchExpressions.values | values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch. | array |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.selector.matchLabels | matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed. | object |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.storageClassName | storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1 | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.volumeMode | volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec. | string |
spec.monitoring.prometheus.volumes.ephemeral.volumeClaimTemplate.spec.volumeName | volumeName is the binding reference to the PersistentVolume backing this claim. | string |
spec.monitoring.prometheus.volumes.fc | fc represents a Fibre Channel resource that is attached to a kubelet's host machine and then exposed to the pod. | object |
spec.monitoring.prometheus.volumes.fc.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. TODO: how do we prevent errors in the filesystem from compromising the machine | string |
spec.monitoring.prometheus.volumes.fc.lun | lun is Optional: FC target lun number | integer |
spec.monitoring.prometheus.volumes.fc.readOnly | readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.fc.targetWWNs | targetWWNs is Optional: FC target worldwide names (WWNs) | array |
spec.monitoring.prometheus.volumes.fc.wwids | wwids Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously. | array |
spec.monitoring.prometheus.volumes.flexVolume | flexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. | object |
spec.monitoring.prometheus.volumes.flexVolume.driver | driver is the name of the driver to use for this volume. | string |
spec.monitoring.prometheus.volumes.flexVolume.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". The default filesystem depends on FlexVolume script. | string |
spec.monitoring.prometheus.volumes.flexVolume.options | options is Optional: this field holds extra command options if any. | object |
spec.monitoring.prometheus.volumes.flexVolume.readOnly | readOnly is Optional: defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.flexVolume.secretRef | secretRef is Optional: secretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts. | object |
spec.monitoring.prometheus.volumes.flexVolume.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.flocker | flocker represents a Flocker volume attached to a kubelet's host machine. This depends on the Flocker control service being running | object |
spec.monitoring.prometheus.volumes.flocker.datasetName | datasetName is Name of the dataset stored as metadata -> name on the dataset for Flocker should be considered as deprecated | string |
spec.monitoring.prometheus.volumes.flocker.datasetUUID | datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset | string |
spec.monitoring.prometheus.volumes.gcePersistentDisk | gcePersistentDisk represents a GCE Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk | object |
spec.monitoring.prometheus.volumes.gcePersistentDisk.fsType | fsType is filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk TODO: how do we prevent errors in the filesystem from compromising the machine | string |
spec.monitoring.prometheus.volumes.gcePersistentDisk.partition | partition is the partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as "1". Similarly, the volume partition for /dev/sda is "0" (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk | integer |
spec.monitoring.prometheus.volumes.gcePersistentDisk.pdName | pdName is unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk | string |
spec.monitoring.prometheus.volumes.gcePersistentDisk.readOnly | readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk | boolean |
spec.monitoring.prometheus.volumes.gitRepo | gitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod's container. | object |
spec.monitoring.prometheus.volumes.gitRepo.directory | directory is the target directory name. Must not contain or start with '..'. If '.' is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name. | string |
spec.monitoring.prometheus.volumes.gitRepo.repository | repository is the URL | string |
spec.monitoring.prometheus.volumes.gitRepo.revision | revision is the commit hash for the specified revision. | string |
spec.monitoring.prometheus.volumes.glusterfs | glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/glusterfs/README.md | object |
spec.monitoring.prometheus.volumes.glusterfs.endpoints | endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod | string |
spec.monitoring.prometheus.volumes.glusterfs.path | path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod | string |
spec.monitoring.prometheus.volumes.glusterfs.readOnly | readOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod | boolean |
spec.monitoring.prometheus.volumes.hostPath | hostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath --- TODO(jonesdl) We need to restrict who can use host directory mounts and who can/can not mount host directories as read/write. | object |
spec.monitoring.prometheus.volumes.hostPath.path | path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath | string |
spec.monitoring.prometheus.volumes.hostPath.type | type for HostPath Volume Defaults to "" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath | string |
spec.monitoring.prometheus.volumes.iscsi | iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://examples.k8s.io/volumes/iscsi/README.md | object |
spec.monitoring.prometheus.volumes.iscsi.chapAuthDiscovery | chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication | boolean |
spec.monitoring.prometheus.volumes.iscsi.chapAuthSession | chapAuthSession defines whether support iSCSI Session CHAP authentication | boolean |
spec.monitoring.prometheus.volumes.iscsi.fsType | fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi TODO: how do we prevent errors in the filesystem from compromising the machine | string |
spec.monitoring.prometheus.volumes.iscsi.initiatorName | initiatorName is the custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface <target portal>:<volume name> will be created for the connection. | string |
spec.monitoring.prometheus.volumes.iscsi.iqn | iqn is the target iSCSI Qualified Name. | string |
spec.monitoring.prometheus.volumes.iscsi.iscsiInterface | iscsiInterface is the interface Name that uses an iSCSI transport. Defaults to 'default' (tcp). | string |
spec.monitoring.prometheus.volumes.iscsi.lun | lun represents iSCSI Target Lun number. | integer |
spec.monitoring.prometheus.volumes.iscsi.portals | portals is the iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). | array |
spec.monitoring.prometheus.volumes.iscsi.readOnly | readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. | boolean |
spec.monitoring.prometheus.volumes.iscsi.secretRef | secretRef is the CHAP Secret for iSCSI target and initiator authentication | object |
spec.monitoring.prometheus.volumes.iscsi.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.iscsi.targetPortal | targetPortal is iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260). | string |
spec.monitoring.prometheus.volumes.name | name of the volume. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names | string |
spec.monitoring.prometheus.volumes.nfs | nfs represents an NFS mount on the host that shares a pod's lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs | object |
spec.monitoring.prometheus.volumes.nfs.path | path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs | string |
spec.monitoring.prometheus.volumes.nfs.readOnly | readOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs | boolean |
spec.monitoring.prometheus.volumes.nfs.server | server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs | string |
spec.monitoring.prometheus.volumes.persistentVolumeClaim | persistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims | object |
spec.monitoring.prometheus.volumes.persistentVolumeClaim.claimName | claimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims | string |
spec.monitoring.prometheus.volumes.persistentVolumeClaim.readOnly | readOnly Will force the ReadOnly setting in VolumeMounts. Default false. | boolean |
spec.monitoring.prometheus.volumes.photonPersistentDisk | photonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine | object |
spec.monitoring.prometheus.volumes.photonPersistentDisk.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. | string |
spec.monitoring.prometheus.volumes.photonPersistentDisk.pdID | pdID is the ID that identifies Photon Controller persistent disk | string |
spec.monitoring.prometheus.volumes.portworxVolume | portworxVolume represents a portworx volume attached and mounted on kubelets host machine | object |
spec.monitoring.prometheus.volumes.portworxVolume.fsType | fSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs". Implicitly inferred to be "ext4" if unspecified. | string |
spec.monitoring.prometheus.volumes.portworxVolume.readOnly | readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.portworxVolume.volumeID | volumeID uniquely identifies a Portworx volume | string |
spec.monitoring.prometheus.volumes.projected | projected items for all in one resources secrets, configmaps, and downward API | object |
spec.monitoring.prometheus.volumes.projected.defaultMode | defaultMode are the mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.projected.sources | sources is the list of volume projections | array |
spec.monitoring.prometheus.volumes.projected.sources.configMap | configMap information about the configMap data to project | object |
spec.monitoring.prometheus.volumes.projected.sources.configMap.items | items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. | array |
spec.monitoring.prometheus.volumes.projected.sources.configMap.items.key | key is the key to project. | string |
spec.monitoring.prometheus.volumes.projected.sources.configMap.items.mode | mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.projected.sources.configMap.items.path | path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. | string |
spec.monitoring.prometheus.volumes.projected.sources.configMap.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.projected.sources.configMap.optional | optional specify whether the ConfigMap or its keys must be defined | boolean |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI | downwardAPI information about the downwardAPI data to project | object |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items | Items is a list of DownwardAPIVolume file | array |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.fieldRef | Required: Selects a field of the pod: only annotations, labels, name and namespace are supported. | object |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.fieldRef.apiVersion | Version of the schema the FieldPath is written in terms of, defaults to "v1". | string |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.fieldRef.fieldPath | Path of the field to select in the specified API version. | string |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.mode | Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.path | Required: Path is the relative path name of the file to be created. Must not be absolute or contain the '..' path. Must be utf-8 encoded. The first item of the relative path must not start with '..' | string |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.resourceFieldRef | Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported. | object |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.resourceFieldRef.containerName | Container name: required for volumes, optional for env vars | string |
spec.monitoring.prometheus.volumes.projected.sources.downwardAPI.items.resourceFieldRef.resource | Required: resource to select | string |
spec.monitoring.prometheus.volumes.projected.sources.secret | secret information about the secret data to project | object |
spec.monitoring.prometheus.volumes.projected.sources.secret.items | items if unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. | array |
spec.monitoring.prometheus.volumes.projected.sources.secret.items.key | key is the key to project. | string |
spec.monitoring.prometheus.volumes.projected.sources.secret.items.mode | mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.projected.sources.secret.items.path | path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. | string |
spec.monitoring.prometheus.volumes.projected.sources.secret.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.projected.sources.secret.optional | optional field specify whether the Secret or its key must be defined | boolean |
spec.monitoring.prometheus.volumes.projected.sources.serviceAccountToken | serviceAccountToken is information about the serviceAccountToken data to project | object |
spec.monitoring.prometheus.volumes.projected.sources.serviceAccountToken.audience | audience is the intended audience of the token. A recipient of a token must identify itself with an identifier specified in the audience of the token, and otherwise should reject the token. The audience defaults to the identifier of the apiserver. | string |
spec.monitoring.prometheus.volumes.projected.sources.serviceAccountToken.expirationSeconds | expirationSeconds is the requested duration of validity of the service account token. As the token approaches expiration, the kubelet volume plugin will proactively rotate the service account token. The kubelet will start trying to rotate the token if the token is older than 80 percent of its time to live or if the token is older than 24 hours.Defaults to 1 hour and must be at least 10 minutes. | integer |
spec.monitoring.prometheus.volumes.projected.sources.serviceAccountToken.path | path is the path relative to the mount point of the file to project the token into. | string |
spec.monitoring.prometheus.volumes.quobyte | quobyte represents a Quobyte mount on the host that shares a pod's lifetime | object |
spec.monitoring.prometheus.volumes.quobyte.group | group to map volume access to Default is no group | string |
spec.monitoring.prometheus.volumes.quobyte.readOnly | readOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false. | boolean |
spec.monitoring.prometheus.volumes.quobyte.registry | registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes | string |
spec.monitoring.prometheus.volumes.quobyte.tenant | tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin | string |
spec.monitoring.prometheus.volumes.quobyte.user | user to map volume access to Defaults to serivceaccount user | string |
spec.monitoring.prometheus.volumes.quobyte.volume | volume is a string that references an already created Quobyte volume by name. | string |
spec.monitoring.prometheus.volumes.rbd | rbd represents a Rados Block Device mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/rbd/README.md | object |
spec.monitoring.prometheus.volumes.rbd.fsType | fsType is the filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd TODO: how do we prevent errors in the filesystem from compromising the machine | string |
spec.monitoring.prometheus.volumes.rbd.image | image is the rados image name. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.rbd.keyring | keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.rbd.monitors | monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | array |
spec.monitoring.prometheus.volumes.rbd.pool | pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.rbd.readOnly | readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | boolean |
spec.monitoring.prometheus.volumes.rbd.secretRef | secretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | object |
spec.monitoring.prometheus.volumes.rbd.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.rbd.user | user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it | string |
spec.monitoring.prometheus.volumes.scaleIO | scaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes. | object |
spec.monitoring.prometheus.volumes.scaleIO.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Default is "xfs". | string |
spec.monitoring.prometheus.volumes.scaleIO.gateway | gateway is the host address of the ScaleIO API Gateway. | string |
spec.monitoring.prometheus.volumes.scaleIO.protectionDomain | protectionDomain is the name of the ScaleIO Protection Domain for the configured storage. | string |
spec.monitoring.prometheus.volumes.scaleIO.readOnly | readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.scaleIO.secretRef | secretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail. | object |
spec.monitoring.prometheus.volumes.scaleIO.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.scaleIO.sslEnabled | sslEnabled Flag enable/disable SSL communication with Gateway, default false | boolean |
spec.monitoring.prometheus.volumes.scaleIO.storageMode | storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned. | string |
spec.monitoring.prometheus.volumes.scaleIO.storagePool | storagePool is the ScaleIO Storage Pool associated with the protection domain. | string |
spec.monitoring.prometheus.volumes.scaleIO.system | system is the name of the storage system as configured in ScaleIO. | string |
spec.monitoring.prometheus.volumes.scaleIO.volumeName | volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source. | string |
spec.monitoring.prometheus.volumes.secret | secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret | object |
spec.monitoring.prometheus.volumes.secret.defaultMode | defaultMode is Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.secret.items | items If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'. | array |
spec.monitoring.prometheus.volumes.secret.items.key | key is the key to project. | string |
spec.monitoring.prometheus.volumes.secret.items.mode | mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set. | integer |
spec.monitoring.prometheus.volumes.secret.items.path | path is the relative path of the file to map the key to. May not be an absolute path. May not contain the path element '..'. May not start with the string '..'. | string |
spec.monitoring.prometheus.volumes.secret.optional | optional field specify whether the Secret or its keys must be defined | boolean |
spec.monitoring.prometheus.volumes.secret.secretName | secretName is the name of the secret in the pod's namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret | string |
spec.monitoring.prometheus.volumes.storageos | storageOS represents a StorageOS volume attached and mounted on Kubernetes nodes. | object |
spec.monitoring.prometheus.volumes.storageos.fsType | fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. | string |
spec.monitoring.prometheus.volumes.storageos.readOnly | readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. | boolean |
spec.monitoring.prometheus.volumes.storageos.secretRef | secretRef specifies the secret to use for obtaining the StorageOS API credentials. If not specified, default values will be attempted. | object |
spec.monitoring.prometheus.volumes.storageos.secretRef.name | Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid? | string |
spec.monitoring.prometheus.volumes.storageos.volumeName | volumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace. | string |
spec.monitoring.prometheus.volumes.storageos.volumeNamespace | volumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod's namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to "default" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created. | string |
spec.monitoring.prometheus.volumes.vsphereVolume | vsphereVolume represents a vSphere volume attached and mounted on kubelets host machine | object |
spec.monitoring.prometheus.volumes.vsphereVolume.fsType | fsType is filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. | string |
spec.monitoring.prometheus.volumes.vsphereVolume.storagePolicyID | storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName. | string |
spec.monitoring.prometheus.volumes.vsphereVolume.storagePolicyName | storagePolicyName is the storage Policy Based Management (SPBM) profile name. | string |
spec.monitoring.prometheus.volumes.vsphereVolume.volumePath | volumePath is the path that identifies vSphere volume vmdk | string |
spec.monitoring.prometheus.volumeMounts | VolumeMounts allows configuration of additional VolumeMounts on the output StatefulSet definition. VolumeMounts specified will be appended to other VolumeMounts in the prometheus container, that are generated as a result of StorageSpec objects. | array |
spec.monitoring.prometheus.volumeMounts.mountPath | Path within the container at which the volume should be mounted. Must not contain ':'. | string |
spec.monitoring.prometheus.volumeMounts.mountPropagation | mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationNone is used. This field is beta in 1.10. | string |
spec.monitoring.prometheus.volumeMounts.name | This must match the Name of a Volume. | string |
spec.monitoring.prometheus.volumeMounts.readOnly | Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false. | boolean |
spec.monitoring.prometheus.volumeMounts.subPath | Path within the volume from which the container's volume should be mounted. Defaults to "" (volume's root). | string |
spec.monitoring.prometheus.volumeMounts.subPathExpr | Expanded path within the volume from which the container's volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container's environment. Defaults to "" (volume's root). SubPathExpr and SubPath are mutually exclusive. | string |
spec.monitoring.grafana | Contains configuration of Grafana to monitor the storage cluster. | object |
spec.monitoring.grafana.enabled | Flag indicating whether Grafana stack needs to be enabled and deployed by the Storage operator. | boolean |
spec.monitoring.telemetry | Contains telemetry configuration for the storage cluster. | object |
spec.monitoring.telemetry.enabled | Flag indicates if telemetry component needs to be enabled | boolean |
spec.monitoring.telemetry.image | Docker image of the telemetry container. | string |
spec.monitoring.telemetry.logUploaderImage | Docker image of the log-upload-service container. | string |