You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloud provider or hardware configuration: Azure AKS
Other info:
After installed, the ksm pod will go into CrashLoopBackOff state with following error log:
╰─➤ k logs kube-state-metrics-58c6d8d7b8-88b8r
unknown flag: --collectors
Usage of /kube-state-metrics:
unknown flag: --collectors
--add_dir_header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files
.
.
.
.
Thanks for your report, I assume this is done via helm? I don't know if helm chart is v2.0 ready, but this flag was renamed to --resources? cc @mrueg@tariq1890
Also I suggest using the k8s.gcr.io/kube-state-metrics/kube-state-metrics:v2.0.0 as v2.0 is out now.
The helm chart is not upgraded yet and we will once we're migrated to the new repository.
Please track prometheus-community/helm-charts#839 and #1448 for further information.
What happened:
Updated image tag to:
What you expected to happen:
kube-state-metrics pod start without any issue
How to reproduce it (as minimally and precisely as possible):
Just update image tag to v2.0.0-rc.1
Anything else we need to know?:
Environment:
kubectl version
):After installed, the ksm pod will go into CrashLoopBackOff state with following error log:
If you check master branch
--collectors
option is still present without any conditioning based on the image version tag:https://github.com/kubernetes/kube-state-metrics/blob/master/charts/kube-state-metrics/templates/deployment.yaml#L71
The text was updated successfully, but these errors were encountered: