4.20 Release notes for Edeg Enablement features

Author: sr1kar99

release_notes/ocp-4-20-release-notes.adoc

@@ -114,6 +114,31 @@ For more information, see xref:../edge_computing/ztp-migrate-clusterinstance.ado
 
 With this update, the Cluster etcd Operator introduces alert levels for the `etcdDatabaseQuotaLowSpace` alert, offering administrators timely notifications about low etcd quota usage. This proactive alert system aims to prevent API server instability and allows for effective resource management in managed OpenShift clusters. The alert levels are `info`, `warning`, and `critical`, providing a more granular approach to monitoring etcd quota usage, which results in dynamic etcd quota management and improved overall cluster performance.
 
+[id="ocp-4-20-edge-computing-arbiter-node_{context}"]
+==== Configuring a local arbiter node
+
+You can configure an {product-title} cluster with two control plane nodes and one local arbiter node to retain high availability (HA) while reducing infrastructure costs for your cluster.
+
+A local arbiter node is a lower-cost, co-located machine that participates in control plane quorum decisions. Unlike a standard control plane node, the arbiter node does not run the full set of control plane services. You can use this configuration to maintain HA in your cluster with only two fully provisioned control plane nodes instead of three.
+
+This feature is now Generally Available.
+
+For more information, see xref:../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc#installing-ocp-agent-local-arbiter-node_installing-with-agent-based-installer[Configuring a local arbiter node].
+
+[id="ocp-4-20-edge-computing-two-node-fencing_{context}"]
+==== Configuring a two-node OpenShift cluster with fencing (Technology Preview)
+
+A two-node OpenShift cluster with fencing provides high availability (HA) with a reduced hardware footprint. This configuration is designed for distributed or edge environments where deploying a full three-node control plane cluster is not practical.
+
+A two-node cluster does not include compute nodes. The two control plane machines run user workloads in addition to managing the cluster.
+
+[NOTE]
+====
+You can deploy a two-node OpenShift cluster with fencing by using either the user-provisioned infrastructure method or the installer-provisioned infrastructure method.
+====
+
+For more information, see xref:../installing/installing_two_node_cluster/installing_tnf/installing-two-node-fencing.adoc#installing-two-node-fencing_installing-two-node-fencing[Preparing to install a two-node OpenShift cluster with fencing].
+
 [id="ocp-release-notes-extensions_{context}"]
 === Extensions ({olmv1})
 
@@ -2108,6 +2133,16 @@ In the following tables, features are marked with the following statuses:
 |Technology Preview
 |Technology Preview
 |Technology Preview
+
+|Configuring a local arbiter node
+|Not Available
+|Technology Preview
+|General Availability
+
+|Configuring a two-node OpenShift cluster with fencing
+|Not Available
+|Not Available
+|Technology Preview
 |====