-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.12.0
-
None
-
No
-
False
-
-
The scheduler-no-bind-address rule has been disabled on newer versions of OpenShift since the parameter was removed.
Description of problem:
A new install of OpenShift with the current OpenShift compliance operator installs fails on the `scheduler-no-bind-address` Compliance Rule. This rule checks to ensure there is no external access to the OpenShift Scheduler and fails, however the port which is reviewed is not inuse.
Version-Release number of selected component (if applicable):
OpenShift: 4.12.0 OpenShift Compliance: 0.1.61
How reproducible:
Everytime
Steps to Reproduce:
1. Install a new cluster 2. Install Compliance Operator 3. Run a CIS test
Actual results:
The `scheduler-no-bind-address` rule fails.
Expected results:
The `scheduler-no-bind-address` should pass
Additional info:
The port `10251` is no longer used by OpenShift so this shouldn't fail as a security issue. It was replaced with port `10259`, which is intended to be a secure port.
