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
OCPBUGS-14399: Minor fix to support protectKernelDefaults
field in Kubelet Config
#3736
OCPBUGS-14399: Minor fix to support protectKernelDefaults
field in Kubelet Config
#3736
Conversation
Skipping CI for Draft Pull Request. |
9415821
to
9e9f67a
Compare
/test ? |
@sairameshv: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
/test unit |
/test e2e-hypershift |
e2e-hypershift is broken, should be hopefully fixed by openshift/hypershift#2664 |
9e9f67a
to
2bc340b
Compare
/retest |
`protectKernelDefaults` field is an upstream, optional boolean field in the Kubelet Configuration Recently, this has been defaulted to `true` in the OCP So, even if the user inputs the field to `false`, this gets omitted due to the tag Added a minor workaround to detect if the user has set the field to `false` Signed-off-by: Sai Ramesh Vanka <svanka@redhat.com>
2bc340b
to
4daf7bf
Compare
/retest |
2 similar comments
/retest |
/retest |
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
Needs lgtm from node team
/assign @rphillips
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: harche, sairameshv, sinnykumari 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 |
@sairameshv: The following test failed, say
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. |
16969b5
into
openshift:master
/jira refresh |
/cherry-pick release-4.13 |
@sairameshv: new pull request created: #3757 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. |
protectKernelDefaults
field in Kubelet ConfigprotectKernelDefaults
field in Kubelet Config
/jira refresh |
@sairameshv: Jira Issue OCPBUGS-14399 is in a security level that is not in the allowed security levels for this repo.
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. |
/jira refresh |
@rphillips: Jira Issue OCPBUGS-14399: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-14399 has not 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. |
/jira refresh |
@rphillips: Jira Issue OCPBUGS-14399: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-14399 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. |
"Fixes: https://issues.redhat.com/browse/OCPBUGS-14399"
- What I did
Added a small workaround to support the
protectKernelDefaults
field of the Kubelet Config when user sets it tofalse
- How to verify it
Apply the following kubeletconfig to the OCP cluster and observe that the same has been reflected in the /etc/kubernetes/kubelet.conf file of the worker nodes
- Description for the changelog
protectKernelDefaults
is set totrue
in the OCP by default recently. Now, configuring this field viakubeletconfig
tofalse
doesn't take effect due to this behavior.This PR adds a minor fix that allow a user to set the field to
false