TLS support about node-cert-exporter HOT 2 CLOSED

Hi @lentzi90 Thanks for your input. However I suggest you look at kube-rbac-proxy which will solve this for you. You run node-cert-exporter with kube-rbac-proxy as a side-car container terminating TLS connections before forwarding to node-cert-exporter. As an example, you put this additional container in the daemonset for node-cert-exporter:

- image: quay.io/brancz/kube-rbac-proxy:v0.8.0
  name: kube-rbac-proxy
  args:
  - --logtostderr
  - --secure-listen-address=[$(IP)]:9100
  - --upstream=http://127.0.0.1:9100/
  env:
  - name: IP
    valueFrom:
      fieldRef:
        fieldPath: status.podIP
  ports:
  - containerPort: 9100
    hostPort: 9100
    name: https

from node-cert-exporter.

Hi and thanks for the comment!

We have considered a side-car solution but would prefer "native" TLS support in node-cert-exporter. This is because we want to keep the footprint as minimal as possible and the complexity low. Do you think this would make it reasonable to add TLS support?

I can create a PR where we can more easily discuss the technical details of it!

from node-cert-exporter.