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
When a managed resource is backed up and subsequently restored using a tool like https://velero.io the newly restored managed resource should resume reconciliation of the external resource that was created by the backed up resource. This should be true for all Azure managed resources that support the crossplane.io/external-name annotation. This annotation set and/or records the actual name of an external resource, causing the newly restored managed resource to use that name.
How could Crossplane help solve your problem?
Crossplane could ensure all Azure managed resources support the crossplane.io/external-name annotation. I believe the following resources need updating:
AKSCluster
(Storage) Container
(Storage) Account
ResourceGroup
VirtualNetwork
Subnet
MySQLServerVirtualNetworkRule
PostgreSQLServerVirtualNetworkRule
The text was updated successfully, but these errors were encountered:
What problem are you facing?
When a managed resource is backed up and subsequently restored using a tool like https://velero.io the newly restored managed resource should resume reconciliation of the external resource that was created by the backed up resource. This should be true for all Azure managed resources that support the
crossplane.io/external-name
annotation. This annotation set and/or records the actual name of an external resource, causing the newly restored managed resource to use that name.How could Crossplane help solve your problem?
Crossplane could ensure all Azure managed resources support the
crossplane.io/external-name
annotation. I believe the following resources need updating:AKSCluster
Container
Account
ResourceGroup
VirtualNetwork
Subnet
MySQLServerVirtualNetworkRule
PostgreSQLServerVirtualNetworkRule
The text was updated successfully, but these errors were encountered: