This is a cache of https://docs.openshift.com/container-platform/4.14/post_installation_configuration/index.html. It is a snapshot of the page at 2024-11-28T14:40:07.757+0000.
Postinstallation configuration overview | Postinstallation configuration | OpenShift Container Platform 4.14
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Postinstallation configuration overview

After installing OpenShift Container Platform, a cluster administrator can configure and customize the following components:

  • Machine

  • Bare metal

  • Cluster

  • Node

  • Network

  • Storage

  • Users

  • Alerts and notifications

Post-installation configuration tasks

You can perform the post-installation configuration tasks to configure your environment to meet your need.

The following lists details these configurations:

  • Configure operating system features: The Machine Config Operator (MCO) manages MachineConfig objects. By using the MCO, you can configure nodes and custom resources.

  • Configure bare metal nodes: You can use the Bare Metal Operator (BMO) to manage bare metal hosts. The BMO can complete the following operations:

    • Inspects hardware details of the host and report them to the bare metal host.

    • Inspect firmware and configure BIOS settings.

    • Provision hosts with a desired image.

    • Clean disk contents for the host before or after provisioning the host.

  • Configure cluster features. You can modify the following features of an OpenShift Container Platform cluster:

    • Image registry

    • Networking configuration

    • Image build behavior

    • Identity provider

    • The etcd configuration

    • Machine set creation to handle the workloads

    • Cloud provider credential management

  • Configuring a private cluster: By default, the installation program provisions OpenShift Container Platform by using a publicly accessible DNS and endpoints. To make your cluster accessible only from within an internal network, configure the following components to make them private:

    • DNS

    • ingress Controller

    • API server

  • Perform node operations: By default, OpenShift Container Platform uses Red Hat Enterprise Linux CoreOS (RHCOS) compute machines. You can perform the following node operations:

    • Add and remove compute machines.

    • Add and remove taints and tolerations.

    • Configure the maximum number of pods per node.

    • Enable Device Manager.

  • Configure users: OAuth access tokens allow users to authenticate themselves to the API. You can configure OAuth to perform the following tasks:

  • Specify an identity provider

  • Use role-based access control to define and supply permissions to users

  • Install an Operator from OperatorHub

  • Configuring alert notifications: By default, firing alerts are displayed on the Alerting UI of the web console. You can also configure OpenShift Container Platform to send alert notifications to external systems.