Title: Storage Error and Duplicate Reconciliation Leading to Resource Synchronization Issue

[helloxjade]

Title: Storage Error and Duplicate Reconciliation Leading to Resource Synchronization Issue

[camilamacedo86]

Hi @helloxjade,

I'd like to note that reconciliation will be triggered under the following circumstances:

• When events are raised for the resources observed/watched, such as when you create, delete, or update a CR managed by the controller, or any other kind of Kubernetes resource it uses or requires which has a watch implementation. More information can be found here.
• By default, every 10 hours, as configured in the main.go / manager.
• When an error occurs, prompting the reconciliation to be re-triggered.

I have some comments inline with your observations:

The error message indicates a storage error (StorageError), with a description mentioning a precondition failure, likely due to a mismatch in the UID of the object.

Without the specific error details, it's challenging to offer targeted help. However, it seems the issue may relate to your implementation rather than a problem with Kubebuilder or its functionality.

Despite no error messages being present, and requeue being set to false.

This comment suggests that your implementation MAYBE is not fully align with the Operator pattern and the design principles adopted by controller-runtime / kubebuilder.

It's essential to aim for idempotent outcomes in your controller logic, specifying the intended actions for creating, deleting, and updating resources. Deviating from ensuring idempotent solutions violates the core principles of this approach.

I recommend dedicating 20 minutes to review the following documentation. It could provide valuable insights into how to ideally structure your solution and understand its workings better.

• https://book.kubebuilder.io/getting-started
• https://book.kubebuilder.io/cronjob-tutorial/gvks

I hope that the info above help you out solve your scenario.
However, see that it does not have too much that we can do to help you out based in your description beyond of the above info.

In this way, if after check the above content provide and your solution you see that you still needing "support help" OR that kubebuilder has one issue, please feel free to raise a new one.

In this case, please provide more info such as:

• that allows us to reproduce the scenario
• that has the info/error faced so that we can have a better idea

I hope that you do not mind but I am closing this one.
You can either try to get help in kubebuilder and controller-runtime slack channels.

Cheers,