diff --git a/docs/examples/prometheus/README.md b/docs/examples/prometheus/README.md index a251e6491..873c094de 100644 --- a/docs/examples/prometheus/README.md +++ b/docs/examples/prometheus/README.md @@ -9,3 +9,9 @@ kubectl apply -f rabbitmq-podmonitor.yaml Alternatively, if you deployed the Prometheus Operator via the [kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) Helm chart, set the values in [kube-prometheus-stack-values.yaml.example](kube-prometheus-stack-values.yaml.example) when installing / upgrading the Helm chart. + +--- +## TLS Endpoints + +With `TLS` enabled you should use `-tls` files to deploy the secure prometheus endpoints. +_Note_: The standard Prometheus (15692) port is disabled with the option `disableNonTLSListeners=true`. \ No newline at end of file diff --git a/docs/examples/prometheus/kube-prometheus-stack-values-tls.yaml.example b/docs/examples/prometheus/kube-prometheus-stack-values-tls.yaml.example new file mode 100644 index 000000000..f20eda71e --- /dev/null +++ b/docs/examples/prometheus/kube-prometheus-stack-values-tls.yaml.example @@ -0,0 +1,14 @@ +--- +prometheus: + additionalPodMonitors: + - name: rabbitmq + podMetricsEndpoints: + - port: prometheus-tls + scheme: https + tlsConfig: + insecureSkipVerify: true + selector: + matchLabels: + app.kubernetes.io/component: rabbitmq + namespaceSelector: + any: true \ No newline at end of file diff --git a/docs/examples/prometheus/rabbitmq-podmonitor-tls.yaml b/docs/examples/prometheus/rabbitmq-podmonitor-tls.yaml new file mode 100644 index 000000000..2abbf665b --- /dev/null +++ b/docs/examples/prometheus/rabbitmq-podmonitor-tls.yaml @@ -0,0 +1,15 @@ +--- +apiVersion: monitoring.coreos.com/v1 +kind: PodMonitor +metadata: + name: rabbitmq +spec: + podMetricsEndpoints: + - interval: 15s + scheme: https + port: prometheus-tls + selector: + matchLabels: + app.kubernetes.io/component: rabbitmq + namespaceSelector: + any: true