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.

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

Allow to set Azure location/region in extra specs #14

Open
pothos opened this issue Feb 15, 2024 · 3 comments
Open

Allow to set Azure location/region in extra specs #14

pothos opened this issue Feb 15, 2024 · 3 comments

Comments

@pothos
Copy link
Contributor

pothos commented Feb 15, 2024

Since one can easily hit resource limits in a region it would be nice to have a way of spreading the pools over multiple regions. Currently one would need to define the provider multiple times.
It would be a nice improvement if one could set the location in the extra specs per pool. Having multiple pools requires labels to distinguish them - this label could be created automatically by deriving it from the location.

@gabriel-samfira
Copy link
Member

This would require some changes to the GARM external provider API, which would send extra specs for all operations not just CreateInstance. Will do with the next GARM release.

@maciejgwizdala
Copy link

maciejgwizdala commented Dec 5, 2024

Hello,
Thanks a lot for your work around GARM - I just started to test it and looks great!
I would like to spread pools over multiple Azure regions like @pothos mentioned.
As it was a while since this case was created and few new GARM releases appeared in the meantime, I would like to ask you @gabriel-samfira, if there is possibility to add this feature?

Best regards,
Maciej Gwizdala

@gabriel-samfira
Copy link
Member

Hi @maciejgwizdala

I think it should be possible now with the recent changes in GARM, but we need to allocate some time to do it, which is in short supply right now.

Until we get around to adding this, as a workaround, you can try to duplicate the provider definition in the config. I know it's not ideal, but it should work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants