Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate

HighLevel 1Manual reviewopenshift

Description

etcd should be configured to make use of TLS encryption for client connections. 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.

OpenShift uses X.509 certificates to provide secure communication to etcd. OpenShift configures these automatically. OpenShift does not use the etcd-certfile or etcd-keyfile flags. Certificates are used for encrypted communication between etcd member peers, as well as encrypted client traffic. The following certificates are generated and used by etcd and other processes that communicate with etcd: • Peer certificates: Used for communication between etcd members. • Client certificates: Used for encrypted server-client communication.

How it is fixed

Fix method: Guidance or infrastructure patch

OpenShift automatically manages TLS and client certificate authentication for etcd. This is not configurable.

Properties

Operating systems: Any
Tags: openshiftapi-serveretcd
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 1.2.25 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate