marcel/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd.git synced 2026-02-20 01:28:45 +01:00
Code Issues Packages Projects Releases Wiki Activity

Revert "chore(docs): update all installs to use --server-side (#25538)"

Browse Source 
This reverts commit 9acb8f815c.
This commit is contained in:
Regina Voloshin
2025-12-09 11:42:41 +02:00
committed by GitHub
parent fa873d4085
commit 050dce8694
13 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.goreleaser.yaml
View File

@@ -66,14 +66,14 @@ release:
```shell
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/{{.Tag}}/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/{{.Tag}}/manifests/install.yaml
```
### HA:
```shell
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/{{.Tag}}/manifests/ha/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/{{.Tag}}/manifests/ha/install.yaml
```
## Release Signatures and Provenance

2
docs/developer-guide/development-environment.md
View File

@@ -109,7 +109,7 @@ make install-codegen-tools-local
```shell
kubectl create namespace argocd &&
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml
```
Set kubectl config to avoid specifying the namespace in every kubectl command.

4
docs/developer-guide/running-locally.md
View File

@@ -21,7 +21,7 @@ First push the installation manifest into argocd namespace:
```shell
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f manifests/install.yaml
kubectl apply -n argocd --force -f manifests/install.yaml
```
The services you will start later assume you are running in the namespace where Argo CD is installed. You can set the current context default namespace as follows:
@@ -245,5 +245,5 @@ make manifests-local
The final step is to push the manifests to your cluster, so it will pull and run your image:
```bash
kubectl apply -n argocd --server-side -f manifests/install.yaml
kubectl apply -n argocd --force -f manifests/install.yaml
```

2
docs/getting_started.md
View File

@@ -13,7 +13,7 @@
```bash
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
```
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.

2
docs/index.md
View File

@@ -21,7 +21,7 @@ Application deployment and lifecycle management should be automated, auditable,
```bash
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
```
Follow our [getting started guide](getting_started.md). Further user oriented [documentation](user-guide/)

2
docs/operator-manual/applicationset/Controlling-Resource-Modification.md
View File

@@ -283,7 +283,7 @@ cd applicationset/manifests
# as described in the previous section.
# Apply the change to the cluster
kubectl apply -n argocd --server-side -f install.yaml
kubectl apply -n argocd -f install.yaml
```
## Preserving changes made to an Applications annotations and labels

4
docs/operator-manual/applicationset/Getting-Started.md
View File

@@ -29,7 +29,7 @@ The ApplicationSet controller *must* be installed into the same namespace as the
Presuming that Argo CD is installed into the `argocd` namespace, run the following command:
```bash
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/applicationset/v0.4.0/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/applicationset/v0.4.0/manifests/install.yaml
```
Once installed, the ApplicationSet controller requires no additional setup.
@@ -47,7 +47,7 @@ The `manifests/install.yaml` file contains the Kubernetes manifests required to
Development builds of the ApplicationSet controller can be installed by running the following command:
```bash
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/applicationset/master/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/applicationset/master/manifests/install.yaml
```
With this option you will need to ensure that Argo CD is already installed into the `argocd` namespace.

2
docs/operator-manual/core.md
View File

@@ -58,7 +58,7 @@ Example:
```
export ARGOCD_VERSION=<desired argo cd release version (e.g. v2.7.0)>
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/$ARGOCD_VERSION/manifests/core-install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/$ARGOCD_VERSION/manifests/core-install.yaml
```
## Using

4
docs/operator-manual/managed-by-url.md
View File

@@ -121,11 +121,11 @@ To test the annotation with two local Argo CD instances:
```bash
# Install primary instance
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
# Install secondary instance
kubectl create namespace namespace-b
kubectl apply -n namespace-b --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl apply -n namespace-b -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
# Port forward both instances
kubectl port-forward -n argocd svc/argocd-server 8080:443 &

2
docs/operator-manual/notifications/index.md
View File

@@ -11,7 +11,7 @@ So you can just use them instead of reinventing new ones.
* Install Triggers and Templates from the catalog
```bash
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/notifications_catalog/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/notifications_catalog/install.yaml
```
* Add email username and password token to the `argocd-notifications-secret` secret

4
docs/operator-manual/upgrading/overview.md
View File

@@ -20,13 +20,13 @@ command to upgrade Argo CD. Make sure to replace `<version>` with the required v
**Non-HA**:
```bash
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/install.yaml
```
**HA**:
```bash
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/ha/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/ha/install.yaml
```
> [!WARNING]

8
docs/proposals/decouple-application-sync-user-using-impersonation.md
View File

@@ -194,7 +194,7 @@ In this specific scenario, service account name `generic-deployer` will get used
- Install ArgoCD in the `argocd` namespace.
```shell
kubectl apply --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
```
- Enable the impersonation feature in ArgoCD.
@@ -258,7 +258,7 @@ In this specific scenario, service account name `guestbook-deployer` will get us
- Install ArgoCD in the `argocd` namespace.
```shell
kubectl apply --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
```
- Enable the impersonation feature in ArgoCD.
@@ -326,7 +326,7 @@ spec:
- Install ArgoCD in the `argocd` namespace.
```shell
kubectl apply --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
```
- Enable the impersonation feature in ArgoCD.
@@ -399,7 +399,7 @@ spec:
- Install ArgoCD in the `argocd` namespace.
```shell
kubectl apply --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/master/manifests/install.yaml -n argocd
```
- Enable the impersonation feature in ArgoCD.

2
docs/try_argo_cd_locally.md
View File

@@ -30,7 +30,7 @@ This command verifies that `kubectl` is pointed to the right cluster.
You can now install Argo CD on your `kind` cluster. First, apply the Argo CD manifest to create the necessary resources:
```bash
kubectl create namespace argocd
kubectl apply -n argocd --server-side -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
```
## Expose ArgoCD API Server