You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 :
Official documentation: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
The text was updated successfully, but these errors were encountered: