Alert rule: EspejoteManagedResourceReadinessChanges

Please consider opening a PR to improve this runbook if you gain new information about causes of the alert, or how to debug or resolve the alert. Click "Edit this Page" in the top right corner to create a PR directly on GitHub.

Overview

This alert fires a managed resource changes between ready and not ready.

The most likely cause is a template applying different manifests depending on the trigger data. There might also be a conflict between Espejote and another controller.

Steps for debugging

Check events on the managed resource

Espejote reports error information as events on the managed resource.

MR_NAME=
MR_NAMESPACE=
kubectl events -n "$MR_NAMESPACE" --for "managedresource/${MR_NAME}"

An explanation of the different error states can be found in the EspejoteManagedResourceNotReady runbook.