master‐config.yaml in Open Shift - unix1998/technical_notes GitHub Wiki

OpenShift have master-config.yaml file, and it isprimary configuration file for the OpenShift cluster, specifically for the master node(s). However, it's important to note that it's mainly used for configuring OpenShift in development or experimental environments.

Here's a breakdown of the master-config.yaml file and its role in OpenShift cluster configuration:

  • Master Node Configuration:

    • The master-config.yaml file defines configuration options for the OpenShift API server and other services running on the master node(s) of the cluster. These options include:
      • API server settings (like listening address, authentication methods).
      • Etcd configuration (if etcd is running on the master nodes).
      • Networking configuration for the master node(s).
      • Security settings for the OpenShift control plane components.
  • Development and Experimental Use:

    • The master-config.yaml file is primarily intended for development or experimental setups where you have more control over the configuration.
    • In production deployments, it's generally recommended to use the standard OpenShift installation process, which leverages tools like the OpenShift installer and pre-configured configuration files. This approach ensures a more standardized and secure cluster setup.
  • Alternative Configuration Methods (Production):

    • During a production installation, OpenShift uses various configuration files and mechanisms, including:
      • Installer configuration files: These files specify the desired cluster configuration for the OpenShift installer.
      • Cluster manifests: These are Kubernetes YAML manifests that define the desired state of the OpenShift cluster components.
      • Machine configs: These files define the configuration for the worker nodes in the cluster.

In essence:

While master-config.yaml offers configuration options for the OpenShift master node, it's primarily for development or experimental use. Production deployments typically rely on the OpenShift installer and other configuration mechanisms for a more robust and secure cluster setup.