Skip to content

[Volcano Enhancement Proposal] Capacity plugin features and design changes #2

Description

@hajnalmt

VEP: Capacity plugin design changes

Summary

Currently I have several issues with the plugin itself, most of them are coming from the fragile architecture the current hierarchical queue design has. In this enhancemanent propsal I try unfold the issues step by step.

Motivation

  • Why this change is needed
  • What problem it solves
  • Who benefits from it

Goals

  • Clear, measurable goals
  • What success looks like

Non‑Goals

  • What is explicitly not included

Proposal

Describe the design, architecture, or workflow changes.

Implementation Plan

  • Write initial design doc
  • Gather feedback from maintainers
  • Finalize API changes
  • Implement feature in code
  • Add tests
  • Update documentation
  • Release in version X.Y

Risks and Mitigations

  • Potential issues
  • How to reduce or avoid them

Alternatives Considered

  • Other approaches you evaluated

Open Questions

  • Question 1
  • Question 2
  • Question 3

Documentation Updates

  • This feature requires design or user documentation changes.
  • If documentation changes are required, I will ensure the relevant documents are updated and published to the Volcano official website (https://volcano.sh) via the volcano-sh/website repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions