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

Add support for priority classes #15

Closed
SansGuidon opened this issue Mar 4, 2022 · 1 comment
Closed

Add support for priority classes #15

SansGuidon opened this issue Mar 4, 2022 · 1 comment
Assignees
Labels
4.4 enhancement New feature or request

Comments

@SansGuidon
Copy link

Is your feature request related to a problem? Please describe.
Context : in our production cluster, some workloads such as neo4j database are more critical than others so we need that reflected in terms of priority classes for pods. We need to ensure those workloads have very high priority so our cluster is functional. Unfortunately the Neo4J helm charts do not expose priorityClassName attribute, which is not blocking but forces us to find workarounds.

Describe the solution you'd like
Something like neo4j-contrib/neo4j-helm#250 and #1
Official documentation: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

Describe alternatives you've considered
Using kustomize to post-render Neo4j helm chart.

Additional context
Related issue : neo4j-contrib/neo4j-helm#227
Related PRs :

@harshitsinghvi22
Copy link
Contributor

@MorganGeek
Support for priority classes released in 4.4.9
https://github.com/neo4j/helm-charts/releases/tag/4.4.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.4 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants