Description
Describe the bug a clear and concise description of what the bug is.
Error with liveness and readiness when kube-rbac-proxy is enabled. Both use https scheme but don't have auth
Readiness probe failed: Get "https://xxx:8081/readyz": dial tcp xxx:8081: connect: connection refused
Liveness probe failed: HTTP probe failed with statuscode: 401
Container kube-state-metrics failed liveness probe, will be restarted
What's your helm version?
version.BuildInfo{Version:"v3.17.2", GitCommit:"cc0bbbd6d6276b83880042c1ecb34087e84d41eb", GitTreeState:"clean", GoVersion:"go1.23.7"}
What's your kubectl version?
Client Version: v1.29.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.5
Which chart?
kube-state-metrics
What's the chart version?
5.32.0
What happened?
I have checked this changes :
6a3be8f
I saw there are used https scheme for Readiness and Liveness in kube-state-metrics container
What you expected to happen?
Pod kube-state-metrics can Running well
How to reproduce it?
If possible, use scheme http for Readiness and Liveness
Currently, I just downgrade to the chart version 5.26.0 or app.kubernetes.io/version is 2.13.0
Enter the changed values of values.yaml?
volumeMounts:
- name: kube-state-metrics-secret
mountPath: /tls/private
readOnly: true
prometheus:
monitor:
enabled: false
kubeRBACProxy:
enabled: true
extraArgs:
- --tls-cert-file=/tls/private/tls.crt
- --tls-private-key-file=/tls/private/tls.key
- --client-ca-file=/tls/private/ca.crt
volumeMounts:
- name: kube-state-metrics-secret
mountPath: /tls/private
readOnly: true
volumes:
- name: kube-state-metrics-secret
secret:
secretName: kube-state-metrics-secret
items:
- key: tls.crt
path: tls.crt
- key: tls.key
path: tls.key
- key: ca.crt
path: ca.crt
Enter the command that you execute and failing/misfunctioning.
helm install kube-state-metrics prometheus-community/kube-state-metrics --version 5.32.0 --values values.yaml
Anything else we need to know?
I can use my custom auth for kube-rbac-proxy container, but I don't know how to make kube-state-metrics container use my custom auth for probes since its scheme uses https