Automatic Broker Relist on Resource Creation Failures

[jzelinskie]

For more context see #1086

Besides a timer-based automatic relist and and manual API driven relist, there might be reconciliation actions that make sense to cause a relist.

This is definitely not something I'd consider required for beta, but valuable ideas for future UX improvements, especially for Brokers that are developing quickly.

Examples

Practical Example: I attempt to create an instance of a plan that has been deleted, but we haven't yet synchronized with the Broker since that plan was deleted. After this failure, it's obvious that the first thing the user will do is synchronize. It makes sense that this could be done for them.

Outlandish speculation: Communication with Brokers during reconciliation could provide hints that a service/plan will be changed/deprecated and this could be used to influence when the next scheduled relist occurs.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.