Describe the bug
after running this command:
helm install zabbix cetic/zabbix --dependency-update -f %HOMEPATH%/zabbix_values.yaml -n monitoring
the postgresql pod fails to start:
C:\workspace>kubectl get pods -n monitoring
NAME READY STATUS RESTARTS AGE
zabbix-0 2/2 Running 0 9m34s
zabbix-postgresql-0 0/1 Pending 0 9m34s
zabbix-web-85d5876bf7-s92bz 0/1 Running 4 9m34s
Version of Helm and Kubernetes:
Helm: v3.6.3
Kube client 1.21.2 Server 1.16.3
What happened:
pod fails to start with this warning:
pod has unbound immediate PersistentVolumeClaims
What you expected to happen:
pod starts sucessfully and reaches running state
How to reproduce it (as minimally and precisely as possible):
helm install zabbix cetic/zabbix --dependency-update -f %HOMEPATH%/zabbix_values.yaml -n monitoring
Describe the bug after running this command: helm install zabbix cetic/zabbix --dependency-update -f %HOMEPATH%/zabbix_values.yaml -n monitoring the postgresql pod fails to start: C:\workspace>kubectl get pods -n monitoring NAME READY STATUS RESTARTS AGE zabbix-0 2/2 Running 0 9m34s zabbix-postgresql-0 0/1 Pending 0 9m34s zabbix-web-85d5876bf7-s92bz 0/1 Running 4 9m34s
Version of Helm and Kubernetes: Helm: v3.6.3 Kube client 1.21.2 Server 1.16.3
What happened: pod fails to start with this warning: pod has unbound immediate PersistentVolumeClaims
What you expected to happen: pod starts sucessfully and reaches running state
How to reproduce it (as minimally and precisely as possible): helm install zabbix cetic/zabbix --dependency-update -f %HOMEPATH%/zabbix_values.yaml -n monitoring
Anything else we need to know: