Skip to content

[Feature]: Whitelist Azure F-Series instances (Or just F16s_v2) #2632

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

Closed
ASmedberg-woolpert opened this issue May 13, 2025 · 2 comments · Fixed by #2647
Closed

[Feature]: Whitelist Azure F-Series instances (Or just F16s_v2) #2632

ASmedberg-woolpert opened this issue May 13, 2025 · 2 comments · Fixed by #2647
Assignees
Labels

Comments

@ASmedberg-woolpert
Copy link

Problem

This is just a me problem, but the Azure F series instances happen to represent the right RAM/CPU ratio for my work (Very similar to the C series on AWS). My understanding is there is a whitelist for each instance type, and all of the F series is not on it.

Solution

I also understand there is some testing that goes into getting a new instance type or types onto the whitelist. If that could be done and added for either the F series or just the F16s_v2, that would help me greatly.

Workaround

Spend some extra money to use more RAM I don't need. (not the end of the world)

Would you like to help us implement this feature by sending a PR?

No

@r4victor
Copy link
Collaborator

r4victor commented May 15, 2025

@ASmedberg-woolpert, thanks for the issue. We need to improve the representation of CPU-only offers across clouds. I'll update the supported Azure series and include compute-optimized Fsv2-series.

@r4victor
Copy link
Collaborator

A similar issue for GCP #2496

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

Successfully merging a pull request may close this issue.

2 participants