// Module included in the following assemblies:
//
//  installing/installing_bare_metal/upi/installing-bare-metal.adoc

:_mod-docs-content-type: PROCEDURE
[id="upi-install-config-local-arbiter-node_{context}"]
= Configuring a local arbiter node by using user-provisioned infrastructure

[role="_abstract"]
To retain high availability (HA) while reducing infrastructure costs for your cluster, you can configure an {product-title} cluster with two control plane nodes and one local arbiter node.

.Prerequisites

* You have downloaded {oc-first} and the installation program.
* You have logged into the {oc-first}.

.Procedure

. Edit the `install-config.yaml` file to define the arbiter node alongside control plane nodes.
+
.Example `install-config.yaml` configuration for deploying an arbiter node
[source,yaml]
----
apiVersion: v1
baseDomain: devcluster.openshift.com
compute:
  - architecture: amd64
    hyperthreading: Enabled
    name: worker
    platform: {}
    replicas: 0
   
arbiter: 
  architecture: amd64
  hyperthreading: Enabled
  replicas: 1 
  name: <Specifies a name for the arbiter machine pool>
  platform:
    baremetal: {}
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    baremetal: {}
  replicas: 2 

platform:
  none: {}

----
+
Set the `arbiter.replicas` field to `1` for the arbiter pool. You cannot set this field to a value that is greater than 1.
+
For `controlPlane.replicas` field, when an arbiter pool is defined, two control plane replicas are valid.

. Save the modified `install-config.yaml` file.
