Many (all?) of our examples are based on built-in individual kubectl commands which can be cumbersome. From feedback, we could suggest some 3rd party tools (e.g. k9s) that make the debugging process easier.
When deploying CAP, pods can restart/go into temporary CLBOs due to dependencies on other pods. From a user perspective, it can appear as if the deployment is not working resulting in manual intervention. E.g. the autoscaler pod will CLBO until autoscaler metrics is up
We should define the relationship between pods and their respective ordering
When it is confirmed that something has gone wrong, list areas users should inspect
What is the debugging process when an app push fails
kubectl
commands which can be cumbersome. From feedback, we could suggest some 3rd party tools (e.g.k9s
) that make the debugging process easier.