Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for delayed provisioning of resources to support topology awareness #156

Closed
bassam opened this issue Nov 23, 2018 · 1 comment
Closed

Add support for delayed provisioning of resources to support topology awareness #156

bassam opened this issue Nov 23, 2018 · 1 comment
Assignees
@ichekrygin
Labels
roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap

Comments

@bassam
Copy link
Member

bassam commented Nov 23, 2018

We should add support for a resourceBindingMode: WaitForFirstConsumer on resources like MySqlInstance and Bucket. This would enable the resource to be created when it first used in a workload, and would enable us to create the resource in a region/zone close to where the workload will run. It will also enable a number of topology/region/location aware scheduling smartness.
@jbw976 jbw976 added this to the v0.2 milestone Jan 18, 2019
@jbw976 jbw976 removed this from the v0.2 milestone Apr 2, 2019
@jbw976 jbw976 added the roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap label Jun 10, 2019
@muvaf
Copy link
Member

muvaf commented Apr 21, 2022 •
edited
Loading

This would enable the resource to be created when it first used in a workload, and would enable us to create the resource in a region/zone close to where the workload will run.

I'm not sure if this is really possible today given that Crossplane doesn't really know when a resource is used especially with the fact that providers are developed completely separately (this wasn't the case back in 2018). We could think of ways to achieve this maybe by checking whether the Secret is mounted by a Pod but it feels out of scope of the project. Feel free to re-open if you think this is still relevant.

@muvaf muvaf closed this as completed Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ichekrygin ichekrygin

Labels
roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ichekrygin @bassam @jbw976 @muvaf