Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[helm] Add Support for Generating Specific Priority Classes in Helm Chart #6025

Open
pkoutsovasilis opened this issue Nov 13, 2024 · 1 comment
Assignees
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@pkoutsovasilis
Copy link
Contributor

Describe the enhancement:
Extend the Helm chart to support the creation of specific Kubernetes PriorityClasses. This will allow users to define and manage the priority of agent pods, ensuring that critical workloads are given appropriate precedence in a resource-constrained environment.

Describe a specific use case for the enhancement or feature:
In scenarios where multiple workloads are running in the same Kubernetes cluster, it is crucial to prioritize elastic-agent pods that perform essential tasks. By configuring specific PriorityClasses through the Helm chart, users can ensure that important agent workloads receive higher scheduling priority compared to less critical processes, optimizing resource allocation and maintaining system reliability.

What is the definition of done?

  • The Helm chart can define and generate custom PriorityClasses based on user configuration.
  • Documentation is updated to guide users on how to set and apply these PriorityClasses.
@pkoutsovasilis pkoutsovasilis added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Nov 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

3 participants