Deleting the pod command didn't work.
I fixed the issue by deleting the entire namespace and then triggering again a make apply:
kubectl delete namespace activemqcd /root/bom/manifests && make apply && cd -
Answered
How to resolve a CrashLoopBackOff on K8S for ActiveMQ?
After changing some configuration in the following files:
- vi bom/manifests/bases/activemq/service.yml
- vi bom/manifests/bases/activemq/deploy.yml
- vi bom/manifests/bases/activemq/kustomization.yml
for the ActiveMQ pod, I tried to execute a make apply with the following commandcd /root/bom/manifests && make apply && cd -
and consequently the activemq-1 instance got in a CrashLoopBackOff state. activemq-0 instance was not rebooting instead.
14 Views
1
Answer
2 years ago
2 years ago
Tags