Skip to content

Conversation

@guoqinwill
Copy link
Contributor

@guoqinwill guoqinwill commented Sep 10, 2025

What type of PR is this?

/kind bug

What this PR does / why we need it:

Starting from version 1.32, kube-scheduler supports retrieving volumeattachment to accurately calculate CSILimits. Volcano also needs to be updated accordingly. For details, see the Kubernetes pr:kubernetes/kubernetes#127757

Which issue(s) this PR fixes:

Fixes # See the Kubernetes issue:kubernetes/kubernetes#126502

Special notes for your reviewer:

Does this PR introduce a user-facing change?


@volcano-sh-bot volcano-sh-bot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 10, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @guoqinwill, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Volcano scheduler to integrate with Kubernetes' recent enhancements for CSILimits calculations. By incorporating VolumeAttachment information, the scheduler can now make more accurate and informed decisions regarding volume-related constraints, ensuring better alignment with upstream Kubernetes behavior and improved scheduling performance.

Highlights

  • RBAC Permissions Update: The scheduler's service account now has permissions to list and watch VolumeAttachment resources under the storage.k8s.io API group. This is crucial for the scheduler to access necessary information for CSILimits calculations.
  • Scheduler Cache Enhancement: The Volcano scheduler's cache has been updated to include a VolumeAttachment informer. This allows the scheduler to actively watch and maintain an up-to-date state of VolumeAttachment objects, improving the accuracy of its scheduling decisions related to CSI volumes.
  • CSILimits Plugin Accuracy: This pull request aligns Volcano with recent Kubernetes updates (v1.32+) by enabling the CSILimits plugin to leverage VolumeAttachments for more precise volume capacity calculations. This ensures better resource utilization and scheduling efficiency.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@volcano-sh-bot volcano-sh-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 10, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to improve the accuracy of the CSILimits plugin by using VolumeAttachments, aligning Volcano with recent changes in kube-scheduler. The changes include adding the necessary RBAC permissions for volumeattachments in the Helm chart and setting up a VolumeAttachmentInformer in the scheduler cache. The implementation is straightforward and correct. The changes look good to me.

@Monokaix
Copy link
Member

So there will be a rbac permission error in volcano when using pvc?

sc.scInformer = informerFactory.Storage().V1().StorageClasses()
sc.scInformer.Informer()
sc.vaInformer = informerFactory.Storage().V1().VolumeAttachments()
sc.vaInformer.Informer()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where this sc.vaInformer been used?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Volcano scheduler’s predicate plugin, the Filter method from k8s.io/kubernetes/pkg/scheduler/framework/plugins/nodevolumelimits is already used for volume-related pre-filtering. As shown in [Kubernetes PR #127757](https://github.com/kubernetes/kubernetes/pull/127757/files), nodevolumelimits already includes validation for VolumeAttachments. Therefore, it seems this PR may not be necessary.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we need to know the accurate error.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The InformerFactory stared first in volcano, it's late to register informer in kube-scheduler plugin, so we shoulld register it before infromerFactory start. @kingeasternsun

Copy link
Contributor

@kingeasternsun kingeasternsun Sep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The InformerFactory stared first in volcano, it's late to register informer in kube-scheduler plugin, so we shoulld register it before infromerFactory start. @kingeasternsun

Got it. This comment could be resolved.
Ignore my comment @guoqinwill .

@Monokaix
Copy link
Member

/approve

@volcano-sh-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Monokaix

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@volcano-sh-bot volcano-sh-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 17, 2025
@JesseStutler
Copy link
Member

/lgtm

@volcano-sh-bot volcano-sh-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2025
@volcano-sh-bot volcano-sh-bot merged commit 85b4ae0 into volcano-sh:master Sep 17, 2025
19 checks passed
@Monokaix
Copy link
Member

Please also cherryick to release1.12 and 1.11

@guoqinwill
Copy link
Contributor Author

Please also cherryick to release1.12 and 1.11
Only release1.12 requires a cherry-pick, because 1.11 is version 1.31, and the use of VA for CSILimits starts from 1.32.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants