From 7823ccd678d018a8da8e4dd08f5488b7da20ee5b Mon Sep 17 00:00:00 2001
From: Saurabh Parekh <sjparekh@amazon.com>
Date: Sun, 22 Sep 2024 18:17:18 -0700
Subject: [PATCH] Add loadBalancerInterface as an optional configuration to the
 baremetal configuration docs

---
 docs/content/en/docs/getting-started/baremetal/bare-spec.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/content/en/docs/getting-started/baremetal/bare-spec.md b/docs/content/en/docs/getting-started/baremetal/bare-spec.md
index e4210e9eefdf6..f55f93bd6fa9c 100644
--- a/docs/content/en/docs/getting-started/baremetal/bare-spec.md
+++ b/docs/content/en/docs/getting-started/baremetal/bare-spec.md
@@ -301,6 +301,9 @@ EKS Anywhere for Bare Metal uses `kube-vip` load balancer by default to expose t
 You can disable this feature by setting this field to `true`.
 >**_NOTE:_** If you skip load balancer deployment, you will have to ensure that the Tinkerbell stack is available at [tinkerbellIP]({{< relref "#tinkerbellip-required" >}}) once the cluster creation is finished. One way to achieve this is by using the [MetalLB]({{< relref "../../packages/metallb" >}}) package.
 
+### loadBalancerInterface (optional)
+Optional field to configure a custom load balancer interface for Tinkerbell stack.
+
 ## TinkerbellMachineConfig Fields
 In the example, there are `TinkerbellMachineConfig` sections for control plane (`my-cluster-name-cp`) and worker (`my-cluster-name`) machine groups.
 The following fields identify information needed to configure the nodes in each of those groups.