Add Intel GPU (Habana Gaudi) autoscaler support

[DorWeinstock]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Add support for Intel Habana Gaudi GPUs in the cluster autoscaler by:

• Define ResourceIntelGPU resource name (habana.ai/gaudi)
• Add Intel GPU to GPUVendorResourceNames list
• Refactor GPU detection logic to iterate through all GPU vendor resource names instead of checking vendors individually

This enables the autoscaler to properly detect and handle Intel GPU nodes alongside existing NVIDIA, AMD, and DirectX GPU support.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Changes has been tested against IBM cloud provider.

Does this PR introduce a user-facing change?

pods can now reuqest habana.ai/gaudi as a valid resource

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: DorWeinstock / name: Dor Weinstock (5873c7f, cc49907)

[k8s-ci-robot]

Welcome @DorWeinstock!

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. 😃

[k8s-ci-robot]

Hi @DorWeinstock. 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.

Details

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.

[elmiko]

this makes sense to me, and i think it's a good upgrade. i have a couple questions about using the gpu package a little more.

[DorWeinstock]

func NodeHasGpuAllocatable(node *apiv1.Node) (gpuAllocatableValue int64, hasGpuAllocatable bool) has been implemented and is now being called both in gpu.go and gpu_processor.go
@elmiko, @vadasambar please check now.

[jackfrancis]

@yansun1996 do the non-Intel changes in this PR address your desired changes in #8865 ?

[yansun1996]

@yansun1996 do the non-Intel changes in this PR address your desired changes in #8865 ?

yep @jackfrancis this PR is doing the same changes compared to #8865

[jackfrancis]

/test pull-cluster-autoscaler-e2e-azure-master

[jackfrancis]

/ok-to-test

[jackfrancis]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DorWeinstock, jackfrancis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS [jackfrancis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jackfrancis]

/cherry-pick cluster-autoscaler-release-1.34

[k8s-infra-cherrypick-robot]

@jackfrancis: #8853 failed to apply on top of branch "cluster-autoscaler-release-1.34":

Applying: Add Intel GPU (Habana Gaudi) autoscaler support
Using index info to reconstruct a base tree...
M	cluster-autoscaler/processors/customresources/gpu_processor.go
Falling back to patching base and 3-way merge...
Auto-merging cluster-autoscaler/processors/customresources/gpu_processor.go
CONFLICT (content): Merge conflict in cluster-autoscaler/processors/customresources/gpu_processor.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Add Intel GPU (Habana Gaudi) autoscaler support

Details

In response to this:

/cherry-pick cluster-autoscaler-release-1.34

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.