Customer just upgraded to 0.1.61 on OpenShift version 4.12.26. 

The rhcos4-selinux-confinement-of-daemons rule has been disabled in this release meaning that any daemon could be running in unconfined_t and we would not fail a compliance check for it. The customer does not have any operational issues, more of a security concern that this rule has been fully disabled and not fixed to allow for kubelet to run in unconfined_t. 

The issues I linked mentioned that this is a goal to turn rhcos4-selinux-confinement-of-daemons back on and make an exception for the kubelet process, but I have not seen this issue tracked anywhere so I made a ticket to get an update on this.

  

1.
2.
3.