The IAM pod is stuck in CrashLoopBackOff on a new IFS Cloud K8s installation, and the current pod logs don't show enough detail to explain why, even though network connectivity to the database checks out fine and DB init completed successfully. Where do I look for more detail?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Pull the previous container's logs (the crashed instance, not the current restart) with kubectl logs -p deployment/ifsapp-iam -c ifsapp-iam -n <namespace>, and separately check kubectl get events -n <namespace> — the currently-running container's own logs are often too thin right after a fresh crash loop, while the previous instance's logs and the namespace's events frequently contain the actual failure detail that explains why IAM keeps crashing.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions