Ensure that the --insecure-port argument is set to 0

MediumLevel 1Manual reviewopenshift

Description

Do not bind to insecure port. The benchmark marks this recommendation Manual.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

The openshift-kube-apiserver is served over HTTPS with authentication and authorization; the secure API endpoint is bound to 0.0.0.0:6443 by default. By default the insecure-port argument is set to 0. Note that the openshift-apiserver is not running in the host network namespace. The port is not exposed on the node, but only through the pod network. Run the following command: oc -n openshift-kube-apiserver get endpoints -o jsonpath='{.items[*].subsets[*].ports[*].port}' Verify the return value is 6443.

How it is fixed

Fix method: Guidance or infrastructure patch

Set the openshift-kube-server --insecure-port argument to 0

Properties

Operating systems: Any
Tags: openshiftapi-server
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 1.2.15 Ensure that the --insecure-port argument is set to 0