OSDU pods are in CrashLoopBackOff state
Dear Support Person,
Unfortunately, I could create this case using the web page because the site thinks I am a spammer.
Luckily it gave me this email option.
I have a Kubernetes cluster comprising one master and three worker nodes. Installed OSDU services and observed most pods are in "CrashLoopBackOff".
Here is the list of namespaces.
NAME STATUS AGE
calico-apiserver Active 72d
calico-system Active 72d
default Active 72d
istio-system Active 9d
kube-node-lease Active 72d
kube-public Active 72d
kube-system Active 72d
osdu Active 8d
osdusecure Active 9d
tigera-operator Active 72d
I attached the following files:
- the modified custom-values.yaml,
- the output of the helm dependency update,
- the output of the helm install command
- List of services after the install
- A snapshot of pods
- The output of the kubectl describe pods command
How can I diagnose and fix the issues? Or do you have a solution?
Kind regards,
Feridun Fildis