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
We need to prioritize the deployments for the Operator and Connect. Therefor we need the possibility to add a priorityClassName for those deployments.
Use cases
We had the situation where we needed the Operator and Connect to be scheduled prioritized to other applications. While starting a new cluster, we needed the Operator and Connect prior to all other applications so that the secrets become available as soon as possible.
Proposed solution
Adding a priorityClassName for both deployments as prepared in the PR #178
Summary
We need to prioritize the deployments for the Operator and Connect. Therefor we need the possibility to add a priorityClassName for those deployments.
Use cases
We had the situation where we needed the Operator and Connect to be scheduled prioritized to other applications. While starting a new cluster, we needed the Operator and Connect prior to all other applications so that the secrets become available as soon as possible.
Proposed solution
Adding a priorityClassName for both deployments as prepared in the PR #178
Is there a workaround to accomplish this today?
Not with helm alone.
References & Prior Work
PR in #178
The text was updated successfully, but these errors were encountered: