kubernetes
Add verdacloud cloud provider
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds Verda (formerly DataCrunch) as an in-tree cloud provider for cluster-autoscaler. Verda is a next-generation AI cloud platform offering NVIDIA GPUs ( A100, H100, H200, B200, etc.) for AI/ML workloads.
Features:
- Auto scaling group management
- GPU node support with nvidia.com/gpu resources
- Multi-location support
- Spot and on-demand instance support
Which issue(s) this PR fixes:
N/A - New cloud provider addition
Special notes for your reviewer:
- OWNERS file has commented-out GitHub handles as I'm not yet a Kubernetes org member (will apply for membership)
Does this PR introduce a user-facing change?
yes
Add support for Verda (formerly DataCrunch) cloud provider in cluster-autoscaler, enabling autoscaling of GPU and CPU worker nodes on Verda infrastructure.
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
- :x: - login: @nusmql / name: nusmql . The commit (2b6c29b3e843773a5804cfaa1dc9e6c3658f11f5) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.
![linux-foundation-easycla[bot] avatar](https://avatars.githubusercontent.com/in/17893?v=4 "Published by a pub.dev verified publisher"){kind=small}
Welcome @nusmql!
It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/autoscaler has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @nusmql. Thanks for your PR.
I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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-sigs/prow repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: nusmql Once this PR has been reviewed and has the lgtm label, please assign x13n for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/ok-to-test
@nusmql thanks for the contribution! Could you kindly sign the CLA?
