openstack-helm-infra/prometheus
Phil Sphicas 5d8cf965c1 Prometheus: Allow input of TLS client creds in values.yaml
Some scrape targets require the use of TLS client certificates, which
are specified as filenames as part of the tls_config.

This change allows these client certs and keys to be provided, stores
them in a secret, and mounts them in the pod under /tls_configs.

Example:

    tls_configs:
      kubernetes-etcd:
        ca.pem: |
          -----BEGIN CERTIFICATE-----
          -----END CERTIFICATE-----
        crt.pem: |
          -----BEGIN CERTIFICATE-----
          -----END CERTIFICATE-----
        key.pem: |
          -----BEGIN RSA PRIVATE KEY-----
          -----END RSA PRIVATE KEY-----

    conf:
      prometheus:
        scrape_configs:
          template: |
            scrape_configs:
              - job_name: kubernetes-etcd
                scheme: https
                tls_config:
                  ca_file: /tls_configs/kubernetes-etcd.ca.pem
                  cert_file: /tls_configs/kubernetes-etcd.cert.pem
                  key_file: /tls_configs/kubernetes-etcd.key.pem

Change-Id: I963c65dc39f1b5110b091296b93e2de9cdd980a4
2020-07-31 16:31:52 +00:00
..
templates Prometheus: Allow input of TLS client creds in values.yaml 2020-07-31 16:31:52 +00:00
values_overrides Enable yamllint checks 2020-05-29 19:49:05 +00:00
Chart.yaml Introduces templates linting 2020-06-11 23:29:42 -05:00
requirements.yaml Introduces templates linting 2020-06-11 23:29:42 -05:00
values.yaml Prometheus: Allow input of TLS client creds in values.yaml 2020-07-31 16:31:52 +00:00