From 000924694b739683413bb52f195af7caea52407e Mon Sep 17 00:00:00 2001 From: xuezhaojun Date: Tue, 5 Nov 2024 16:30:34 +0800 Subject: [PATCH] docs: clarify cluster-proxy installation for non-kind clusters Updates the cluster-proxy installation documentation to clarify that non-kind clusters (e.g., OpenShift) require setting the proxyServer.entrypointAddress value. Adds an example helm install command showing how to set this value. Signed-off-by: xuezhaojun --- .../integration/cluster-proxy.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/content/en/docs/getting-started/integration/cluster-proxy.md b/content/en/docs/getting-started/integration/cluster-proxy.md index b18af7c3..61fdd28e 100644 --- a/content/en/docs/getting-started/integration/cluster-proxy.md +++ b/content/en/docs/getting-started/integration/cluster-proxy.md @@ -110,6 +110,23 @@ Then run the following helm command to install the cluster-proxy addon: ```shell $ helm install -n open-cluster-management-addon --create-namespace \ cluster-proxy ocm/cluster-proxy +``` + +**Note:** If you're using a non-Kind cluster, for example, an Openshift cluster, +you need to configure the `ManagedProxyConfiguration` by setting `proxyServer.entrypointAddress` +in the `values.yaml` to the address of the proxy server. + +To do this at install time, you can run the following command: +```shell +$ helm install -n open-cluster-management-addon --create-namespace \ + cluster-proxy ocm/cluster-proxy \ + --set "proxyServer.entrypointAddress=
" +``` + +After the installation, you can check the deployment status of the cluster-proxy +addon by running the following command: + +```shell $ kubectl -n open-cluster-management-addon get deploy NAME READY UP-TO-DATE AVAILABLE AGE cluster-proxy 3/3 3 3 24h