You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource state should be recovered when not present, for example when resources were recovered from a backup.
Implementation proposal
In order to increase general resiliency, the operator can succeed resources when creation fails because the resource already exists on the provider. This would also work in case of recovery from a deleted state.
This would require one-off runs triggered for runconfigurations to have deterministic names (for example including the hash of the RC's triggers)
The text was updated successfully, but these errors were encountered:
Overview
The K8s Operator best practices mention that resource states should always be recoverable if not present.
Feature Request
Resource state should be recovered when not present, for example when resources were recovered from a backup.
Implementation proposal
In order to increase general resiliency, the operator can succeed resources when creation fails because the resource already exists on the provider. This would also work in case of recovery from a deleted state.
This would require one-off runs triggered for runconfigurations to have deterministic names (for example including the hash of the RC's triggers)
The text was updated successfully, but these errors were encountered: