Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1631108

Summary: feature-flags not passed to kubelet with node-config kubeletArguments or proxyArguments
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED NOTABUG QA Contact: DeShuai Ma <dma>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, dzhukous, jokerman, jupierce, mmccomas
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-02 13:35:45 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:
Embargoed:
Attachments:
Description Flags
ineffectual feature-gates configurations none

Description Justin Pierce 2018-09-19 23:06:33 UTC 
Created attachment 1484956 [details]
ineffectual feature-gates configurations

Description of problem:
I tried several variations in node-config.yaml to configure feature-gates for a kubelet in 3.11. In each case, a default set of feature-gates appeared to override my preference. 

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

How reproducible:
100%

Actual results:
See attachments for variations attempted

Expected results:
Based on 3.10 documentation (https://docs.openshift.com/container-platform/3.10/admin_guide/disabling_features.html), setting proxyArguments feature-gates should configure the feature gates.
Comment 3 Justin Pierce 2018-10-02 13:35:45 UTC 
Thanks sjennings - grepping the configmap uncovered my error. There was already a `feature-gates:` entry in the node-config prior to my addition. The original was taking precedence over the `feature-gates` key I was adding. Apologies for the misfire. 

The following are passed successfully to the kubelet. 
>>>>
    kubeletArguments:
      pod-max-pids:
      - '1024'
      feature-gates:
      - RotateKubeletClientCertificate=true,RotateKubeletServerCertificate=true,SupportPodPidsLimit=true
     ....
<<<<

appears on the node as:
>>>>
[root@ip-172-31-56-246 ~]# ps `pidof hyperkube` 
  PID TTY      STAT   TIME COMMAND
27042 ?        Ssl    0:58 /usr/bin/hyperkube kubelet ... --fail-swap-on=false --featu
re-gates=RotateKubeletClientCertificate=true,RotateKubeletServerCertificate=true,SupportPodPidsLimit=true ... --pod-max-pids=1024 ....
<<<<