Skip to content

Commit fe3632f

Browse files
docs: Update Argo CD installation and API server access instructions (argoproj#25120)
Signed-off-by: Revital Barletz <Revital.Barletz@octopus.com> Signed-off-by: Revital Barletz <Revital.barletz@octopus.com>
1 parent 9ee5cca commit fe3632f

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

docs/getting_started.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ kubectl create namespace argocd
1616
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
1717
```
1818

19-
This will create a new namespace, `argocd`, where Argo CD services and application resources will live.
19+
This will create a new `argocd` namespace where all Argo CD services and application resources will reside. It will also install Argo CD by applying the official manifests from the stable branch. Using a pinned version (like `v3.2.0`) is recommended for production.
2020

2121
> [!WARNING]
2222
> The installation manifests include `ClusterRoleBinding` resources that reference `argocd` namespace. If you are installing Argo CD into a different
@@ -55,10 +55,9 @@ Also available in Mac, Linux and WSL Homebrew:
5555
brew install argocd
5656
```
5757
58-
## 3. Access The Argo CD API Server
58+
## 3. Access Argo CD
5959
60-
By default, the Argo CD API server is not exposed with an external IP. To access the API server,
61-
choose one of the following techniques to expose the Argo CD API server:
60+
By default, Argo CD isn’t exposed outside the cluster. To access Argo CD from your browser or CLI, use one of the following methods:
6261
6362
### Service Type Load Balancer
6463
Change the argocd-server service type to `LoadBalancer`:

0 commit comments

Comments
 (0)