Closed siegenthalerroger closed 3 months ago
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
This is still relevant
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
This is still relevant
I totally agree, it is necessary.
@nammn I see the pull request was merged, would it be possible to get a patch or minor release of the community-operator chart to make the functionality available?
That would be great!
@vramperez @siegenthalerroger there is a release planned in around 2-3 weeks.
@nammn I see that a release of the community operator including this change has not been released yet, any news on when the release will be released?
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
This has been releasesd
The community operator should allow setting a
priorityClassName
for the operator deployment from values.yaml.This aligns with other operators and enables the correct usage of priority classes within k8s.