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 priorityClassName to the Manager Container #67

Merged
merged 1 commit into from
Jul 24, 2023

Conversation

razo7
Copy link
Member

@razo7 razo7 commented Jul 10, 2023

Help the scheduler to understand the pod's priority versus other pods to be scheduled.

priorityClassName for other Medik8s operators:

Related links:

Help the scheduler to understand the pod's priority versus other pods to be scheduled
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 10, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@razo7
Copy link
Member Author

razo7 commented Jul 10, 2023

/test 4.13-openshift-e2e

1 similar comment
@razo7
Copy link
Member Author

razo7 commented Jul 17, 2023

/test 4.13-openshift-e2e

@mshitrit
Copy link
Member

Hmm looking at the 3 Three priorityClassName conventions I'm not entirely sure whether system-node-critical or system-cluster-critical is more appropriate here.
As far as I see the only difference is that the latter one can be OOMKilled, which IIUC shouldn't happen as long as it's not using more memory than declared.

  • Am I getting it right ?
  • Any particular reason for choosing system-cluster-critical over system-node-critical ?

@razo7 razo7 changed the title Add priorityClassName to manager container Add priorityClassName to the Manager Container Jul 17, 2023
@slintes
Copy link
Member

slintes commented Jul 17, 2023

we should discuss this more, tbh I doubt that system-cluster-critical or system-node-critical should be used by non core OCP components.

/hold

@razo7
Copy link
Member Author

razo7 commented Jul 24, 2023

Am I getting it right ?

👍🏻

Any particular reason for choosing system-cluster-critical over system-node-critical ?

Consistency with the other operators, since they use system-cluster-critical.

In the last team meeting we have discussed about this topic and AFAIU using system-cluster-critical, as the other operators use, is the less strict priorityClassName out of the two common Kubernetes PriorityClasses and it suits FAR.

@razo7 razo7 marked this pull request as ready for review July 24, 2023 11:34
@openshift-ci openshift-ci bot requested review from clobrano and mshitrit July 24, 2023 11:35
Copy link
Member

@slintes slintes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold cancel

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 24, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: razo7, slintes

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 946af05 into medik8s:main Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants