-
Notifications
You must be signed in to change notification settings - Fork 378
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
Bug 2093046: oc debug: Add priorityClassName into node debugging pod template #1263
Conversation
When user tries to debug a pod, priorityClassName is automatically copied to this debug pod. However, there is no such information for node debugging. This PR adds "openshift-user-critical" priorityClassName into node debugging pod which means that "it is fine node debugging pod to be preempted by user-workload and OOMKilled."
@ardaguclu: This pull request references Bugzilla bug 2093046, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
cc: @stbenjam |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, soltysh 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 |
/retest-required |
/retest-required |
must-gather pod was added exception list because `oc debug node` does not include priorityClassName. After this PR adds openshift/oc/pull/1263 priorityClassName statically, we can remove must-gather pod from priorityclass exception list.
/retest-required |
/retest-required |
5 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
/retest-required |
@ardaguclu: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@ardaguclu: All pull requests linked via external trackers have merged: Bugzilla bug 2093046 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
must-gather pod was added exception list because `oc debug node` does not include priorityClassName. After this PR adds openshift/oc/pull/1263 priorityClassName statically, we can remove must-gather pod from priorityclass exception list.
When user tries to debug a pod, priorityClassName is automatically copied to this debug pod. However, there is no such information for node debugging.
This PR adds "openshift-user-critical" priorityClassName into node debugging pod which means that "it is fine node debugging pod to be preempted by user-workload and OOMKilled."[1]
[1] https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#priority-classes