-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.14.0
-
None
-
Important
-
No
-
SDN Sprint 243
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-20104. The following is the description of the original issue:
—
Description of problem:
The recently introduced node identify feature introduces pods that are running as root. While it's understood there may be situations where that is absolutely required, the goal should be to always run with least privilege / non-root.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Deploy an IBM Managed OpenShift 4.14.0 cluster. I suspect any OpenShift 4.14.0 cluster will have these pods running as root as well.
Actual results:
network-node-identity pods are running as root
Expected results:
network-node-identity pods should be running as non-root
Additional info:
Due to the introduction of these pods running as root in an IBM Managed OpenShift 4.14.0 cluster, we will have to file for a security exception.
- links to
-
RHSA-2023:5006
OpenShift Container Platform 4.14.z security update