helpful in troubleshooting situation if a pod is stuck in init-state then you can check if its because of the dependent pods ...
DEPLOYMENT NAME ================>>> DEPENDENT PODS----------------------------------------------------------------------------------------------------------- axaservices-adminui ======>>> adminui-init-postgresql adminui-init-amq adminui-init-readserver axaservices-axa-user-processor ======>>> axa-user-processor-init-postgresql axaservices-ba-routing-service ======>>> wait-for-kafka axaservices-crashhandler ======>>> crashhandler-init-postgresql crashhandler-init-amq axaservices-ba-routing-service ======>>> wait-for-kafka axaservices-crashhandler ======>>> crashhandler-init-postgresql crashhandler-init-amq axaservices-decryptor ======>>> decryptor-init-postgresql axaservices-indexer ======>>> transformer-init-postgresql transformer-init-amq axaservices-ngutils ======>>> ngutils-init-kafka ngutils-init-api ngutils-init-jaf-namenode ngutils-init-jaf-clientdatanode axaservices-readserver ======>>> readserver-init-postgresql readserver-init-amq readserver-init-jarvis-apis axaservices-scheduler ======>>> scheduler-init-postgresql axaservices-transformer ======>>> transformer-init-postgresql transformer-init-amq doi-adminui ======>>> adminui-init-postgresql adminui-init-jarvis-elasticsearch adminui-init-doi-readserver adminui-init-pod-complete doi-analyticsjobs ======>>> doi-adminui-init-jarvis-apis doi-cpa-ng ======>>> doi-servicemanagement-init-jarvis-elasticsearch doi-servicemanagement-init-doi-readserver doi-dspcasa ======>>> doi-dspcasa-init-postgresql doi-dspcasa1 ======>>> doi-adminui-init-postgresql doi-dspintegrator ======>>> doi-genericapiconnector-init-jarvis-apis doi-genericapiconnector ======>>> doi-genericapiconnector-init-jarvis-apis doi-incidentmanagement ======>>> doi-incidentmanagement-init-doi-nim doi-incidentmanagement-init-doi-tenantmanagement doi-integrationgateway ======>>> doi-integrationgateway-init-jarvis-kafka doi-servicealarm ======>>> doi-servicealarm-init-jarvis-elasticsearch doi-servicealarm-init-doi-readserver doi-servicealarm-init-jarvis-kafka doi-servicemanagement ======>>> doi-servicemanagement-init-jarvis-elasticsearch doi-servicemanagement-init-doi-readserver doi-tenantmanagement ======>>> doi-tenantmanagement-init-postgresql doireadserver ======>>> doi-adminui-init-readserver doi-adminui-init-amq dxi-grafana-deployment ======>>> dxi-grafana-init-postgresql dxi-grafana-services ======>>> dxi-grafana-init-grafana-deployment jaf-clientdatanode ======>>> jaf-clientdatanode-init-jaf-namenode volume-mount-clientdatanode jaf-hadoopconnector ======>>> jaf-hadoopconnector-init-jaf-namenode jaf-jobmanager ======>>> jaf-jobmanager-init-jaf-clientnodemanager jaf-namenode ======>>> jaf-namenode-init-jarvis-apis volume-mount-namenode jaf-resourcemanager1 ======>>> jaf-resourcemanager1-init-jaf-clientdatanode jaf-resourcemanager2 ======>>> jaf-resourcemanager2-init-jaf-clientdatanode jarvis-elasticsearch ======>>> volume-mount-es jarvis-kafka ======>>> volume-mount-kafka jarvis-zookeeper ======>>> volume-mount-zookeeper ng-acc-configserver-deployment ======>>> init-redis ng-acc-repository-deployment ======>>> init-ds selfmonitoring-elastalert ======>>> selfmonitoring-elastalert-init-jarvis-elasticsearch selfmonitoring-filebeat ======>>> selfmonitoring-filebeat-init-selfmonitoring-logstash selfmonitoring-filebeat-init-doi-readserver selfmonitoring-kibana ======>>> selfmonitoring-kibana-init-jarvis-elasticsearch selfmonitoring-logstash ======>>> selfmonitoring-logstash-init-jarvis-elasticsearch