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
Disaster recover or migrating resources to other clusters is hard and scary
How could Crossplane help solve your problem?
During migration or disaster recovery, it will be difficult to set "pause" on all resources. It would be nice to pause a full provider, like a CLI argument --pause.
It would also be nice to have a pause option which would Observe but not Create/Update/Delete. This would give an operator confidence in what kinds of actions would run when the cluster is unpaused. This might be a different CLI option or annotation.
The text was updated successfully, but these errors were encountered:
@luebken my main worry when doing use cases such as
restoring a cluster (recreate, partial restore, go back in time for a namespace) with thousands of managed resources
restore an external resource from backup and then restore and re-attach it to a managed resource
would be that due to some unforeseen issue:
many resources are doubly created, for example due to generateName we get role-HASH2 when we had role-HASH1. For example if just restoring a claim and the composition rendering does not use predicatable name/external-name.
resources are garbage collected, and then, deleted if we only restore managed resource without claims
So I would like to pause Create/Update/Delete but not Observe to ensure everything is as expected. Pause (as implemented today) would not give any comfort similar to a terraform plan, but this might do that.
Just writing down two related ideas here
What problem are you facing?
Disaster recover or migrating resources to other clusters is hard and scary
How could Crossplane help solve your problem?
During migration or disaster recovery, it will be difficult to set "pause" on all resources. It would be nice to pause a full provider, like a CLI argument
--pause
.It would also be nice to have a pause option which would Observe but not Create/Update/Delete. This would give an operator confidence in what kinds of actions would run when the cluster is unpaused. This might be a different CLI option or annotation.
The text was updated successfully, but these errors were encountered: