OpenShift hosts

Internal

• OpenShift 3.5. Installation

Overview

Documentation for https://github.com/NovaOrdis/playground/blob/master/openshift/3.5/hosts

Defaults are available here:

https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_metrics/defaults/main.yaml

Ansible Configuration

ansible_become

If ansible_ssh_user is not root, ansible_become must be set to true and the user must be configured for passwordless sudo.

ansible_ssh_user

The ssh user used by Ansible to connect to hosts. This user should allow ssh based authentication without requiring a password, and also it should allow passwordless sudo to root. If using ssh key based authentication, then the key should be managed by an ssh agent. Also see ansible_become.

General Settings

debug_level

Describes which INFO messages are logged to the systemd-journald.service. Set one of the following:

• 0 to log errors and warnings only
• 2 to log normal information (default)
• 4 to log debugging-level information
• 6 to log API-level (request/response) debugging information
• 8 to log body-level API debugging information

This can also be configured after installation by following the procedure described here: Change the Log Level for OpenShift Processes.

containerized

If set to true, containerized OpenShift services (instead of RPM-based) are run on all nodes. The default is "false", which means the default RPM method is used. RHEL Atomic Host requires the containerized method, which is automatically selected for you based on the detection of the /run/ostree-booted file. Since 3.1.1.

deployment_type

Deployment type ("origin" or "openshift-enterprise").

For more details see:

https://docs.openshift.com/container-platform/3.5/install_config/install/advanced_install.html#advanced-install-deployment-types

Logging Configuration

openshift_hosted_logging_deploy

OpenShift Logging Concepts