The Troubleshooting page under Installation mentions the possibility that pods are not starting because a per-deployment task has failed. This should be updated to mention the blockDeployment parameter that can be set in the KeptnConfig resource so that a failed task does not block the deployment. Setting this parameter seems like the easiest way to determine if this is the problem.
DoD
installation/troubleshooting explains how to use the blockDeployment parameter to determine if a failed pre-deployment task is blocking the pods from starting
Summary
The Troubleshooting page under Installation mentions the possibility that pods are not starting because a per-deployment task has failed. This should be updated to mention the
blockDeployment
parameter that can be set in the KeptnConfig resource so that a failed task does not block the deployment. Setting this parameter seems like the easiest way to determine if this is the problem.DoD
blockDeployment
parameter to determine if a failed pre-deployment task is blocking the pods from starting