Changes in node-exporter daemonset are persistent and does not get revert back to default configuration

Issue

• Suppose, the value TLS_RSA_WITH_AES_128_CBC_SHA256 is deleted from tls-cipher-suites argument mentioned in kube-rbac-proxy container spec.

# oc edit ds node-exporter

- --tls-cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

• After deletion and saving the changes, node-exporter pods were rolled out with the above configuration. As observed, the node-exporter daemonset never changed and reconciling to the default configuration never happened and the change made to daemonset is persistent.