Bug 1921248

Summary: Clarify the kubelet configuration cr description
Product: OpenShift Container Platform Reporter: Ryan Phillips <rphillips>
Component: NodeAssignee: Harshal Patil <harpatil>
Node sub component: Kubelet QA Contact: MinLi <minmli>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, minmli
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:56:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ryan Phillips 2021-01-27 19:12:46 UTC
Description of problem:
It is extremely difficult to validate all known Kubelet Configuration options. We had this debate when we began the project if we should open up all the KubeletConfiguration options or just a subset. We agreed on opening the entire structure up to allow for any configuration (similar to how we did it in Openshift 3.x).

For these reasons, we cannot add an unlimited amount of validation to the CR object for Kubelet configuration options. There is a risk associated to setting the options. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 MinLi 2021-02-03 08:09:02 UTC
There is a little flaw in this fix, for "important" is misspelled to "importent" in 3rd line of DESCRIPTION

$ oc explain kubeletconfig.spec.kubeletConfig --recursive=true
KIND:     KubeletConfig
VERSION:  machineconfiguration.openshift.io/v1

DESCRIPTION:
     The fields of the kubelet configuration are defined in kubernetes upstream.
     Please refer to the types defined in the version/commit used by OpenShift
     of the upstream kubernetes. It's importent to note that, since the fields
     of the kubelet configuration are directly fetched from upstream the
     validation of those values is handled directly by the kubelet. Please refer
     to the upstream version of the relavent kubernetes for the valid values of
     these fields. Invalid values of the kubelet configuration fields may render
     cluster nodes unusable.


$ oc get clusterversion 
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-02-02-223803   True        False         124m    Cluster version is 4.7.0-0.nightly-2021-02-02-223803

Comment 4 MinLi 2021-02-07 07:07:26 UTC
verified on version: 4.7.0-0.nightly-2021-02-06-084550

Comment 7 errata-xmlrpc 2021-02-24 15:56:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633