Troubleshooting

If we face issues with our infrastructure API, these tips could help us debug the problem in the best possible way:

• Status attributes and events are essential elements to debug issues. These details can be viewed by running kubectl describe on the given resource.
• When we start looking for issues, we take a top-down approach. This is because Crossplane follows the same convention as Kubernetes to hold the errors close to the resource where it happens.
• The debugging order will be claim, then XR, and then each composing resource. We should start with a claimed object. If we cannot locate the issue, we go deep into the XR and then the composing resources.
• spec.resourceRef from the claim description can help us to identify the XR name. Again, the same attribute can be used to find the composing resources from the XR.

Make an intentional mistake in the resource configuration of the composition to go through the debugging experience. You learn more...