Skip to content
Open
Changes from 10 commits
Commits
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
8 changes: 3 additions & 5 deletions docs/getting_started.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,7 @@
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
```

This will create a new namespace, `argocd`, where Argo CD services and application resources will live.
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.

> [!WARNING]
> The installation manifests include `ClusterRoleBinding` resources that reference `argocd` namespace. If you are installing Argo CD into a different
Expand Down Expand Up @@ -55,10 +54,9 @@ Also available in Mac, Linux and WSL Homebrew:
brew install argocd
```

## 3. Access The Argo CD API Server
## 3. Access Argo CD

By default, the Argo CD API server is not exposed with an external IP. To access the API server,
choose one of the following techniques to expose the Argo CD API server:
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically, it is the api-server tha makes more sense to be here. I would recommend adding a link to the architecture docs here. Just saying Argo CD means all the components can't be exposed outside the cluster whereas in reality, it's only one component of Argo CD i.e. api-server which is not exposed with an external IP.

Copy link
Contributor Author

@revitalbarletz revitalbarletz Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should remain abstract and we should refer to Argo CD rather than Argo CD API - its a getting started guide and the component were not described yet here. It seems more of a high level document to me. @todaywasawesome / @crenshaw-dev what do you think?


### Service Type Load Balancer
Change the argocd-server service type to `LoadBalancer`:
Expand Down
Loading