Skip to content

Conversation

@aaradhychinche-alt
Copy link

Summary

This PR adds an initial introduction and usage guide for the Hierarchical Queue feature under the Key Features section.

Changes

  • Added a new Hierarchical Queue documentation page
  • Explained the motivation for hierarchical queues
  • Described the difference between capacity and proportion queue models
  • Outlined common use cases

This is a follow-up to the Key Features foundation and contributes to improving feature documentation on the website.

Refs #330

@volcano-sh-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign thor-wl for approval. For more information see the Kubernetes Code Review Process.

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

Details 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

@gemini-code-assist
Copy link

Summary of Changes

Hello @aaradhychinche-alt, 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 significantly enhances the project's documentation by adding a comprehensive introduction to the Hierarchical Queue feature. It clarifies the core concept, explains why such a feature is crucial in modern cluster management, and differentiates between the available queue models, thereby providing a foundational understanding for users and administrators. This addition is a step towards improving the overall feature documentation on the website.

Highlights

  • New Documentation Page: Introduced a new documentation page for the 'Hierarchical Queue' feature under the 'Key Features' section.
  • Feature Introduction: Provided an initial introduction to Hierarchical Queues, explaining their purpose in organizing workloads into multi-level queues for fine-grained resource management and fair sharing.
  • Motivation Explained: Detailed the necessity of Hierarchical Queues in shared Kubernetes clusters to address resource competition, provide isolation, enforce quotas, and improve fairness.
  • Queue Models: Described two primary queue models supported by Volcano: 'Capacity Queue' (for maximum resource limits and strong isolation) and 'Proportion Queue' (for percentage-based resource allocation and fair sharing).
  • Use Cases: Outlined typical use cases for Hierarchical Queues, including multi-tenant clusters, AI/big data platforms, and enterprise environments requiring both fairness and isolation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 19, 2026
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 adds a new documentation page introducing the Hierarchical Queue feature. The new page serves as a good high-level overview. I've suggested a couple of improvements to enhance clarity and accuracy. Specifically, I've recommended clarifying the description of the 'Capacity Queue' model to avoid confusion with the 'capability' property, and adding a link to the existing detailed user guide for hierarchical queues. These changes will make the documentation more accurate and helpful for users.

@volcano-sh-bot volcano-sh-bot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jan 19, 2026
@aaradhychinche-alt
Copy link
Author

@Arhell @kevin-wangzefeng
can You please review this pr when You have time ?

Signed-off-by: Aaradhy Chinche <aaradhychinche@gmail.com>
Signed-off-by: Aaradhy Chinche <aaradhychinche@gmail.com>
@aaradhychinche-alt aaradhychinche-alt force-pushed the docs/hierarchical-queue-feature branch from 80c1991 to 0b7e34d Compare January 24, 2026 05:33
@volcano-sh-bot volcano-sh-bot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants