From fa46df27c13546cc8ac009793225fcd3f612b33c Mon Sep 17 00:00:00 2001 From: Petr McAllister Date: Wed, 8 Nov 2023 16:55:39 -0800 Subject: [PATCH] Add EKS warning to Primary Remote instructions (#13745) * add EKS support statement to Primary Remote instructions * removing trailing spaces --- .../setup/install/multicluster/primary-remote/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/docs/setup/install/multicluster/primary-remote/index.md b/content/en/docs/setup/install/multicluster/primary-remote/index.md index 9ec811f277..38e5ca5d31 100644 --- a/content/en/docs/setup/install/multicluster/primary-remote/index.md +++ b/content/en/docs/setup/install/multicluster/primary-remote/index.md @@ -16,6 +16,13 @@ Before proceeding, be sure to complete the steps under [before you begin](/docs/setup/install/multicluster/before-you-begin). {{< boilerplate multi-cluster-with-metallb >}} +{{< warning >}} +These instructions are not suitable for AWS EKS primary cluster deployment. +The reason behind this incompatibility is that AWS Load Balancers (LB) are +presented as Fully Qualified Domain Names (FQDN), while the remote cluster +utilizes the Kubernetes service type 'ExternalName'. However, the 'ExternalName' +type exclusively supports IP addresses and does not accommodate FQDNs. +{{< /warning >}} In this configuration, cluster `cluster1` will observe the API Servers in both clusters for endpoints. In this way, the control plane will be able to