1 # Default values for prometheus-operator.
2 # This is a YAML-formatted file.
3 # Declare variables to be passed into your templates.
5 ## Provide a name in place of prometheus-operator for `app:` labels
9 ## Provide a name to substitute for the full names of resources
13 ## Labels to apply to all resources
19 ## Create default rules for monitoring the cluster
29 kubePrometheusNodeAlerting: true
30 kubePrometheusNodeRecording: true
32 kubernetesAbsent: true
34 kubernetesResources: true
35 kubernetesStorage: true
36 kubernetesSystem: true
38 prometheusOperator: true
40 ## Labels for default rules
42 ## Annotations for default rules
45 ## Provide custom recording or alerting rules to be deployed into the cluster.
47 additionalPrometheusRules: []
48 # - name: my-rule-file
53 # expr: 100 * my_record
61 ## Reference to one or more secrets to be used when pulling images
62 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
65 # - name: "image-pull-secret"
67 ## Configuration for alertmanager
68 ## ref: https://prometheus.io/docs/alerting/alertmanager/
72 ## Deploy alertmanager
76 ## Service account for Alertmanager to use.
77 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
83 ## Configure pod disruption budgets for Alertmanager
84 ## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
85 ## This configuration is immutable once created and will require the PDB to be deleted to be changed
86 ## https://github.com/kubernetes/kubernetes/issues/45398
93 ## Alertmanager configuration directives
94 ## ref: https://prometheus.io/docs/alerting/configuration/#configuration-file
95 ## https://prometheus.io/webtools/alerting/routing-tree-editor/
113 ## Alertmanager template files to format alerts
114 ## ref: https://prometheus.io/docs/alerting/notifications/
115 ## https://prometheus.io/docs/alerting/notification_examples/
119 # An example template:
120 # template_1.tmpl: |-
121 # {{ define "cluster" }}{{ .ExternalURL | reReplaceAll ".*alertmanager\\.(.*)" "$1" }}{{ end }}
123 # {{ define "slack.myorg.text" }}
125 # {{ range .Alerts }}
126 # *Alert:* {{ .Annotations.summary }} - `{{ .Labels.severity }}`
127 # *Cluster:* {{ template "cluster" $root }}
128 # *Description:* {{ .Annotations.description }}
129 # *Graph:* <{{ .GeneratorURL }}|:chart_with_upwards_trend:>
130 # *Runbook:* <{{ .Annotations.runbook }}|:spiral_note_pad:>
132 # {{ range .Labels.SortedPairs }} • *{{ .Name }}:* `{{ .Value }}`
142 ## Hosts must be provided if Ingress is enabled.
145 # - alertmanager.domain.com
147 ## TLS configuration for Alertmanager Ingress
148 ## Secret must be manually created in the namespace
151 # - secretName: alertmanager-general-tls
153 # - alertmanager.example.com
155 ## Configuration for Alertmanager service
162 ## Port to expose on each node
163 ## Only used if service.type is 'NodePort'
166 ## List of IP addresses at which the Prometheus server service is available
167 ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
171 loadBalancerSourceRanges: []
176 ## If true, create a serviceMonitor for alertmanager
181 ## Settings affecting alertmanagerSpec
182 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#alertmanagerspec
185 ## Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#metadata
186 ## Metadata Labels and Annotations gets propagated to the Alertmanager pods.
190 ## Image of Alertmanager
193 repository: quay.io/prometheus/alertmanager
196 ## Secrets is a list of Secrets in the same namespace as the Alertmanager object, which shall be mounted into the
197 ## Alertmanager Pods. The Secrets are mounted into /etc/alertmanager/secrets/.
201 ## ConfigMaps is a list of ConfigMaps in the same namespace as the Alertmanager object, which shall be mounted into the Alertmanager Pods.
202 ## The ConfigMaps are mounted into /etc/alertmanager/configmaps/.
206 ## Log level for Alertmanager to be configured with.
210 ## Size is the expected size of the alertmanager cluster. The controller will eventually make the size of the
211 ## running cluster equal to the expected size.
214 ## Time duration Alertmanager shall retain data for. Default is '120h', and must match the regular expression
215 ## [0-9]+(ms|s|m|h) (milliseconds seconds minutes hours).
219 ## Storage is the definition of how storage will be used by the Alertmanager instances.
220 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
223 # volumeClaimTemplate:
225 # storageClassName: gluster
226 # accessModes: ["ReadWriteOnce"]
233 ## The external URL the Alertmanager instances will be available under. This is necessary to generate correct URLs. This is necessary if Alertmanager is not served from root of a DNS name. string false
237 ## The route prefix Alertmanager registers HTTP handlers for. This is useful, if using ExternalURL and a proxy is rewriting HTTP routes of a request, and the actual ExternalURL is still true,
238 ## but the server serves requests under a different route prefix. For example for use with kubectl proxy.
242 ## If set to true all actions on the underlying managed objects are not going to be performed, except for delete actions.
246 ## Define which Nodes the Pods are scheduled on.
247 ## ref: https://kubernetes.io/docs/user-guide/node-selection/
251 ## Define resources requests and limits for single Pods.
252 ## ref: https://kubernetes.io/docs/user-guide/compute-resources/
258 ## Pod anti-affinity can prevent the scheduler from placing Prometheus replicas on the same node.
259 ## The default value "soft" means that the scheduler should *prefer* to not schedule two replica pods onto the same node but no guarantee is provided.
260 ## The value "hard" means that the scheduler is *required* to not schedule two replica pods onto the same node.
261 ## The value "" will disable pod anti-affinity so that no anti-affinity rules will be configured.
265 ## If anti-affinity is enabled sets the topologyKey to use for anti-affinity.
266 ## This can be changed to, for example, failure-domain.beta.kubernetes.io/zone
268 podAntiAffinityTopologyKey: kubernetes.io/hostname
270 ## If specified, the pod's tolerations.
271 ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
277 # effect: "NoSchedule"
279 ## SecurityContext holds pod-level security attributes and common container settings.
280 ## This defaults to non root user with uid 1000 and gid 2000. *v1.PodSecurityContext false
281 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
288 ## ListenLocal makes the Alertmanager server listen on loopback, so that it does not bind against the Pod IP.
289 ## Note this is only for the Alertmanager UI, not the gossip communication.
293 ## Containers allows injecting additional containers. This is meant to allow adding an authentication proxy to an Alertmanager pod.
297 ## Priority class assigned to the Pods
299 priorityClassName: ""
301 ## AdditionalPeers allows injecting a set of additional Alertmanagers to peer with to form a highly available cluster.
305 ## Using default values from https://github.com/helm/charts/blob/master/stable/grafana/values.yaml
310 ## Deploy default dashboards.
312 defaultDashboardsEnabled: true
314 adminPassword: prom-operator
317 ## If true, Prometheus Ingress will be created
321 ## Annotations for Prometheus Ingress
324 # kubernetes.io/ingress.class: nginx
325 # kubernetes.io/tls-acme: "true"
327 ## Labels to be added to the Ingress
332 ## Must be provided if Ingress is enable.
335 # - prometheus.domain.com
338 ## TLS configuration for prometheus Ingress
339 ## Secret must be manually created in the namespace
342 # - secretName: prometheus-general-tls
344 # - prometheus.example.com
349 label: grafana_dashboard
352 label: grafana_datasource
354 extraConfigmapMounts: []
355 # - name: certs-configmap
356 # mountPath: /etc/grafana/ssl/
357 # configMap: certs-configmap
360 ## If true, create a serviceMonitor for grafana
365 ## Component scraping the kube api server
368 ## Component scraping the kube api server
373 serverName: kubernetes
374 insecureSkipVerify: false
376 ## If your API endpoint address is not reachable (as in AKS) you can replace it with the kubernetes service
380 # - __meta_kubernetes_namespace
381 # - __meta_kubernetes_service_name
382 # - __meta_kubernetes_endpoint_port_name
384 # regex: default;kubernetes;https
385 # - targetLabel: __address__
386 # replacement: kubernetes.default.svc:443
395 ## Component scraping the kubelet and kubelet-hosted cAdvisor
399 namespace: kube-system
402 ## Enable scraping the kubelet over https. For requirements to enable this see
403 ## https://github.com/coreos/prometheus-operator/issues/926
406 # cAdvisorMetricRelabelings:
407 # - sourceLabels: [__name__, image]
409 # regex: container_([a-z_]+);
412 # - sourceLabels: [__name__]
414 # regex: container_(network_tcp_usage_total|network_udp_usage_total|tasks_state|cpu_load_average_10s)
419 ## Component scraping the kube controller manager
421 kubeControllerManager:
424 ## If your kube controller manager is not deployed as a pod, specify IPs it can be found on
431 ## If using kubeControllerManager.endpoints only the port and targetPort are used
437 k8s-app: kube-controller-manager
438 ## Component scraping coreDns. Use either this or kubeDns
448 ## Component scraping kubeDns. Use either this or coreDns
455 ## Component scraping etcd
460 ## If your etcd is not deployed as a pod, specify IPs it can be found on
467 ## Etcd service. If using kubeEtcd.endpoints only the port and targetPort are used
475 ## Configure secure access to the etcd cluster by loading a secret into prometheus and
476 ## specifying security configuration below. For example, with a secret named etcd-client-cert
480 ## insecureSkipVerify: false
481 ## serverName: localhost
482 ## caFile: /etc/prometheus/secrets/etcd-client-cert/etcd-ca
483 ## certFile: /etc/prometheus/secrets/etcd-client-cert/etcd-client
484 ## keyFile: /etc/prometheus/secrets/etcd-client-cert/etcd-client-key
488 insecureSkipVerify: false
495 ## Component scraping kube scheduler
500 ## If your kube scheduler is not deployed as a pod, specify IPs it can be found on
507 ## If using kubeScheduler.endpoints only the port and targetPort are used
513 k8s-app: kube-scheduler
515 ## Component scraping kube state metrics
520 ## Configuration for kube-state-metrics subchart
528 ## Deploy node exporter as a daemonset to all nodes
533 ## Use the value configured in prometheus-node-exporter.podLabels
537 ## Configuration for prometheus-node-exporter subchart
539 prometheus-node-exporter:
541 ## Add the 'node-exporter' label to be used by serviceMonitor to match standard common usage in rules and grafana dashboards
543 jobLabel: node-exporter
545 - --collector.filesystem.ignored-mount-points=^/(dev|proc|sys|var/lib/docker/.+)($|/)
546 - --collector.filesystem.ignored-fs-types=^(autofs|binfmt_misc|cgroup|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|mqueue|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|sysfs|tracefs)$
548 ## Manages Prometheus and Alertmanager components
553 ## Service account for Alertmanager to use.
554 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
560 ## Configuration for Prometheus operator service
567 ## Port to expose on each node
568 ## Only used if service.type is 'NodePort'
574 ## Only use if service.type is "loadbalancer"
577 loadBalancerSourceRanges: []
580 ## NodepPort, ClusterIP, loadbalancer
584 ## List of IP addresses at which the Prometheus server service is available
585 ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
589 ## Deploy CRDs used by Prometheus Operator.
591 createCustomResource: true
593 ## Customize CRDs API Group
594 crdApiGroup: monitoring.coreos.com
596 ## Attempt to clean up CRDs created by Prometheus Operator.
598 cleanupCustomResource: true
600 ## Labels to add to the operator pod
604 ## Assign a PriorityClassName to pods if set
605 # priorityClassName: ""
608 # Use logfmt (default) or json-formatted logging
611 ## Decrease log verbosity to errors only
614 ## If true, the operator will create and maintain a service for scraping kubelets
615 ## ref: https://github.com/coreos/prometheus-operator/blob/master/helm/prometheus-operator/README.md
619 namespace: kube-system
621 ## Create a servicemonitor for the operator
626 ## Resource limits & requests
636 ## Define which Nodes the Pods are scheduled on.
637 ## ref: https://kubernetes.io/docs/user-guide/node-selection/
641 ## Tolerations for use with node taints
642 ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
648 # effect: "NoSchedule"
650 ## Assign the prometheus operator to run on specific nodes
651 ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
654 # requiredDuringSchedulingIgnoredDuringExecution:
656 # - matchExpressions:
657 # - key: kubernetes.io/e2e-az-name
667 ## Prometheus-operator image
670 repository: quay.io/coreos/prometheus-operator
672 pullPolicy: IfNotPresent
674 ## Configmap-reload image to use for reloading configmaps
676 configmapReloadImage:
677 repository: quay.io/coreos/configmap-reload
680 ## Prometheus-config-reloader image to use for config and rule reloading
682 prometheusConfigReloaderImage:
683 repository: quay.io/coreos/prometheus-config-reloader
686 ## Hyperkube image to use when cleaning up
689 repository: k8s.gcr.io/hyperkube
691 pullPolicy: IfNotPresent
693 ## Deploy a Prometheus instance
699 ## DAaaS: Bring up a default instance when Operator comes up
700 ## set startup as false to bring up only operator.
703 ## Service account for Prometheuses to use.
704 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
710 ## Configuration for Prometheus service
718 ## To be used with a proxy extraContainer port
721 ## List of IP addresses at which the Prometheus server service is available
722 ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
726 ## Port to expose on each node
727 ## Only used if service.type is 'NodePort'
732 ## Only use if service.type is "loadbalancer"
734 loadBalancerSourceRanges: []
742 ## Create role bindings in the specified namespaces, to allow Prometheus monitoring
743 ## a role binding in the release namespace will always be created.
748 ## Configure pod disruption budgets for Prometheus
749 ## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
750 ## This configuration is immutable once created and will require the PDB to be deleted to be changed
751 ## https://github.com/kubernetes/kubernetes/issues/45398
764 ## Must be provided if Ingress is enabled.
767 # - prometheus.domain.com
770 ## TLS configuration for Prometheus Ingress
771 ## Secret must be manually created in the namespace
774 # - secretName: prometheus-general-tls
776 # - prometheus.example.com
781 ## Settings affecting prometheusSpec
782 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec
786 ## Interval between consecutive scrapes.
790 ## Interval between consecutive evaluations.
792 evaluationInterval: ""
794 ## ListenLocal makes the Prometheus server listen on loopback, so that it does not bind against the Pod IP.
798 ## Image of Prometheus.
801 repository: quay.io/prometheus/prometheus
804 ## Tolerations for use with node taints
805 ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
811 # effect: "NoSchedule"
813 ## Alertmanagers to which alerts will be sent
814 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#alertmanagerendpoints
816 ## Default configuration will connect to the alertmanager deployed as part of this release
818 alertingEndpoints: []
824 ## External labels to add to any time series or alerts when communicating with external systems
828 ## External URL at which Prometheus will be reachable.
832 ## Define which Nodes the Pods are scheduled on.
833 ## ref: https://kubernetes.io/docs/user-guide/node-selection/
837 ## Secrets is a list of Secrets in the same namespace as the Prometheus object, which shall be mounted into the Prometheus Pods.
838 ## The Secrets are mounted into /etc/prometheus/secrets/. Secrets changes after initial creation of a Prometheus object are not
839 ## reflected in the running Pods. To change the secrets mounted into the Prometheus Pods, the object must be deleted and recreated
840 ## with the new list of secrets.
844 ## ConfigMaps is a list of ConfigMaps in the same namespace as the Prometheus object, which shall be mounted into the Prometheus Pods.
845 ## The ConfigMaps are mounted into /etc/prometheus/configmaps/.
849 ## Namespaces to be selected for PrometheusRules discovery.
850 ## If nil, select own namespace. Namespaces to be selected for ServiceMonitor discovery.
851 ## See https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#namespaceselector for usage
853 ruleNamespaceSelector: {}
855 ## If true, a nil or {} value for prometheus.prometheusSpec.ruleSelector will cause the
856 ## prometheus resource to be created with selectors based on values in the helm deployment,
857 ## which will also match the PrometheusRule resources created
859 ruleSelectorNilUsesHelmValues: true
861 ## PrometheusRules to be selected for target discovery.
862 ## If {}, select all ServiceMonitors
865 ## Example which select all prometheusrules resources
866 ## with label "prometheus" with values any of "example-rules" or "example-rules-2"
875 ## Example which select all prometheusrules resources with label "role" set to "example-rules"
878 # role: example-rules
880 ## If true, a nil or {} value for prometheus.prometheusSpec.serviceMonitorSelector will cause the
881 ## prometheus resource to be created with selectors based on values in the helm deployment,
882 ## which will also match the servicemonitors created
884 serviceMonitorSelectorNilUsesHelmValues: true
886 ## ServiceMonitors to be selected for target discovery.
887 ## If {}, select all ServiceMonitors
889 serviceMonitorSelector: {}
890 ## Example which selects ServiceMonitors with label "prometheus" set to "somelabel"
891 # serviceMonitorSelector:
893 # prometheus: somelabel
895 ## Namespaces to be selected for ServiceMonitor discovery.
896 ## See https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#namespaceselector for usage
898 serviceMonitorNamespaceSelector: {}
900 ## How long to retain metrics
904 ## If true, the Operator won't process any Prometheus configuration changes
908 ## Number of Prometheus replicas desired
912 ## Log level for Prometheus be configured in
916 ## Prefix used to register routes, overriding externalUrl route.
917 ## Useful for proxies that rewrite URLs.
921 ## Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#metadata
922 ## Metadata Labels and Annotations gets propagated to the prometheus pods.
927 # k8s-app: prometheus
929 ## Pod anti-affinity can prevent the scheduler from placing Prometheus replicas on the same node.
930 ## The default value "soft" means that the scheduler should *prefer* to not schedule two replica pods onto the same node but no guarantee is provided.
931 ## The value "hard" means that the scheduler is *required* to not schedule two replica pods onto the same node.
932 ## The value "" will disable pod anti-affinity so that no anti-affinity rules will be configured.
935 ## If anti-affinity is enabled sets the topologyKey to use for anti-affinity.
936 ## This can be changed to, for example, failure-domain.beta.kubernetes.io/zone
938 podAntiAffinityTopologyKey: kubernetes.io/hostname
940 ## The remote_read spec configuration for Prometheus.
941 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#remotereadspec
943 # - url: http://remote1/read
945 ## The remote_write spec configuration for Prometheus.
946 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#remotewritespec
949 # - url: http://remote1/push
951 ## Resource limits & requests
957 ## Prometheus StorageSpec for persistent data
958 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
961 # volumeClaimTemplate:
963 # storageClassName: gluster
964 # accessModes: ["ReadWriteOnce"]
970 ## AdditionalScrapeConfigs allows specifying additional Prometheus scrape configurations. Scrape configurations
971 ## are appended to the configurations generated by the Prometheus Operator. Job configurations must have the form
972 ## as specified in the official Prometheus documentation:
973 ## https://prometheus.io/docs/prometheus/latest/configuration/configuration/#<scrape_config>. As scrape configs are
974 ## appended, the user is responsible to make sure it is valid. Note that using this feature may expose the possibility
975 ## to break upgrades of Prometheus. It is advised to review Prometheus release notes to ensure that no incompatible
976 ## scrape configs are going to break Prometheus after the upgrade.
978 ## The scrape configuraiton example below will find master nodes, provided they have the name .*mst.*, relabel the
979 ## port to 2379 and allow etcd scraping provided it is running on all Kubernetes master nodes
981 additionalScrapeConfigs: []
982 # - job_name: kube-etcd
983 # kubernetes_sd_configs:
987 # ca_file: /etc/prometheus/secrets/etcd-client-cert/etcd-ca
988 # cert_file: /etc/prometheus/secrets/etcd-client-cert/etcd-client
989 # key_file: /etc/prometheus/secrets/etcd-client-cert/etcd-client-key
992 # regex: __meta_kubernetes_node_label_(.+)
993 # - source_labels: [__address__]
995 # target_label: __address__
996 # regex: ([^:;]+):(\d+)
997 # replacement: ${1}:2379
998 # - source_labels: [__meta_kubernetes_node_name]
1001 # - source_labels: [__meta_kubernetes_node_name]
1003 # target_label: node
1006 # metric_relabel_configs:
1007 # - regex: (kubernetes_io_hostname|failure_domain_beta_kubernetes_io_region|beta_kubernetes_io_os|beta_kubernetes_io_arch|beta_kubernetes_io_instance_type|failure_domain_beta_kubernetes_io_zone)
1011 ## AdditionalAlertManagerConfigs allows for manual configuration of alertmanager jobs in the form as specified
1012 ## in the official Prometheus documentation https://prometheus.io/docs/prometheus/latest/configuration/configuration/#<alertmanager_config>.
1013 ## AlertManager configurations specified are appended to the configurations generated by the Prometheus Operator.
1014 ## As AlertManager configs are appended, the user is responsible to make sure it is valid. Note that using this
1015 ## feature may expose the possibility to break upgrades of Prometheus. It is advised to review Prometheus release
1016 ## notes to ensure that no incompatible AlertManager configs are going to break Prometheus after the upgrade.
1018 additionalAlertManagerConfigs: []
1019 # - consul_sd_configs:
1020 # - server: consul.dev.test:8500
1023 # tag_separator: ','
1025 # - metrics-prometheus-alertmanager
1027 ## AdditionalAlertRelabelConfigs allows specifying Prometheus alert relabel configurations. Alert relabel configurations specified are appended
1028 ## to the configurations generated by the Prometheus Operator. Alert relabel configurations specified must have the form as specified in the
1029 ## official Prometheus documentation: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#alert_relabel_configs.
1030 ## As alert relabel configs are appended, the user is responsible to make sure it is valid. Note that using this feature may expose the
1031 ## possibility to break upgrades of Prometheus. It is advised to review Prometheus release notes to ensure that no incompatible alert relabel
1032 ## configs are going to break Prometheus after the upgrade.
1034 additionalAlertRelabelConfigs: []
1036 # regex: prometheus_replica
1040 ## SecurityContext holds pod-level security attributes and common container settings.
1041 ## This defaults to non root user with uid 1000 and gid 2000.
1042 ## https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md
1049 ## Priority class assigned to the Pods
1051 priorityClassName: ""
1053 ## Thanos configuration allows configuring various aspects of a Prometheus server in a Thanos environment.
1054 ## This section is experimental, it may change significantly without deprecation notice in any release.
1055 ## This is experimental and may change significantly without backward compatibility in any release.
1056 ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#thanosspec
1060 ## Containers allows injecting additional containers. This is meant to allow adding an authentication proxy to a Prometheus pod.
1061 ## if using proxy extraContainer update targetPort with proxy container port
1064 ## Enable additional scrape configs that are managed externally to this chart. Note that the prometheus
1065 ## will fail to provision if the correct secret does not exist.
1067 additionalScrapeConfigsExternal: false
1069 additionalServiceMonitors: []
1070 ## Name of the ServiceMonitor to create
1074 ## Additional labels to set used for the ServiceMonitorSelector. Together with standard labels from
1077 # additionalLabels: {}
1079 ## Service label for use in assembling a job name of the form <label value>-<port>
1080 ## If no label is specified, the service name is used.
1084 ## Label selector for services to which this ServiceMonitor applies
1088 ## Namespaces from which services are selected
1090 # namespaceSelector:
1091 ## Match any namespace
1095 ## Explicit list of namespace names to select
1099 ## Endpoints of the selected service to be monitored
1102 ## Name of the endpoint's service port
1103 ## Mutually exclusive with targetPort
1106 ## Name or number of the endpoint's target port
1107 ## Mutually exclusive with port
1110 ## File containing bearer token to be used when scraping targets
1112 # bearerTokenFile: ""
1114 ## Interval at which metrics should be scraped
1118 ## HTTP path to scrape for metrics
1122 ## HTTP scheme to use for scraping
1126 ## TLS configuration to use when scraping the endpoint
1130 ## Path to the CA file
1134 ## Path to client certificate file
1138 ## Skip certificate verification
1140 # insecureSkipVerify: false
1142 ## Path to client key file
1146 ## Server name used to verify host name