Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: clarify cluster-proxy installation for non-kind clusters #436

Merged
merged 1 commit into from
Nov 5, 2024
Merged

docs: clarify cluster-proxy installation for non-kind clusters #436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/en/docs/getting-started/integration/cluster-proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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=<address of the proxy server>"
```

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
Expand Down
Loading