reconciler-logic

To update status without 409 conflicts, apply changes only to the status subresource using `resource.UpdateObject`. This isolates status writes from concurrent spec changes in your grafana-app-sdk operator.

A reconciler loop handles idempotency by tracking `LastObservedGeneration`. It skips unnecessary reconcile actions if the resource generation matches the last observed value, preventing duplicate work on create, update, and resync events.

The best way to poll an asynchronous external job in a Kubernetes reconciler is to return a `RequeueAfter` duration in the `operator.ReconcileResult`. This schedules delayed polling until the external operation transitions states, like Pending to Ready.

To handle resource deletion cleanly in a grafana-app-sdk operator, check for the `ReconcileActionDeleted` action within your `TypedReconciler` logic. This allows you to execute cleanup tasks before the resource is fully removed.

Choose a reconciler pattern over a watcher when you need to drive resources toward a desired state on create, update, delete, or resync events. Watchers are better suited for simple event processing without convergence logic.