redhat-developer / redhat-developer/mapt
Explore using microsoft.compute/skualternativespotvmsize/location type on azure spot algo
Open
Nobody has claimed this yet.
enhancement
priority/LOW
provider/AZURE
size/M
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Inspect if we can use microsoft.compute/skualternativespotvmsize/location to find similar vm sizes with features (nested virtualization) to get a lower price
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Azure microsoft.compute/skualternativespotvmsize/location resource and the existing spot algorithm entry point. Determine whether it can identify VM sizes supporting nested virtualization at a lower price, and document a clear implementation path or why the approach is not viable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100