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
Context
When creating a Subscription on BTP, the subscription to the target application itself can fail. Right now this is reflected at status.atProvider.state as SUBSCRIBE_FAILED. However, sometimes this is expected and can automatically resolve with retrying (reconciling). This is especially relevant when the Subscription would only be successful once other resources are successfully reconciled (e.g. when applying all infrastructure resources at the same time, which is a common pattern with crossplane)
Scope
The pattern of "Eventually consistent" should also be followed here and a retry/recreate should be triggered. I think it would make sense to add a config parameter like recreateOnSubscriptionFailure: true.
Out of scope
Technical Steps
Workarounds & Alternatives
Manually deleting the subscription on BTP UI will fix it, as it will reconcile again and recreate it. Manually deleting the K8s resource does not work because of this issue: #177
Additional context
Unfortunately there is no simple "retry" feature on BTP, technically the subscription needs to be deleted and recreated in order to retry.
The text was updated successfully, but these errors were encountered:
Context
When creating a Subscription on BTP, the subscription to the target application itself can fail. Right now this is reflected at status.atProvider.state as
SUBSCRIBE_FAILED
. However, sometimes this is expected and can automatically resolve with retrying (reconciling). This is especially relevant when the Subscription would only be successful once other resources are successfully reconciled (e.g. when applying all infrastructure resources at the same time, which is a common pattern with crossplane)Scope
The pattern of "Eventually consistent" should also be followed here and a retry/recreate should be triggered. I think it would make sense to add a config parameter like
recreateOnSubscriptionFailure: true
.Out of scope
Technical Steps
Workarounds & Alternatives
Manually deleting the subscription on BTP UI will fix it, as it will reconcile again and recreate it. Manually deleting the K8s resource does not work because of this issue: #177
Additional context
Unfortunately there is no simple "retry" feature on BTP, technically the subscription needs to be deleted and recreated in order to retry.
The text was updated successfully, but these errors were encountered: