Review ArgoCD config tutorial: fix sync policy, typo, add cross-references
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
bec554110a
commit
0698013355
2 changed files with 11 additions and 7 deletions
1
docs/changelog.d/+argocd-config-doc-review.doc.md
Normal file
1
docs/changelog.d/+argocd-config-doc-review.doc.md
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
Review and fix ArgoCD config tutorial: correct sync policy example, fix typo, add missing cross-references and frontmatter.
|
||||||
|
|
@ -1,6 +1,7 @@
|
||||||
---
|
---
|
||||||
title: ArgoCD Config
|
title: ArgoCD Config
|
||||||
modified: 2026-02-07
|
modified: 2026-03-24
|
||||||
|
last-reviewed: 2026-03-24
|
||||||
tags:
|
tags:
|
||||||
- tutorials
|
- tutorials
|
||||||
- replication
|
- replication
|
||||||
|
|
@ -52,7 +53,7 @@ tailscale serve --bg --https 8443 https+insecure://localhost:$(kubectl -n argocd
|
||||||
|
|
||||||
Or create a Tailscale Ingress in Kubernetes (see [[tailscale-operator]]).
|
Or create a Tailscale Ingress in Kubernetes (see [[tailscale-operator]]).
|
||||||
|
|
||||||
Access at `https://your-server.tailnet.ts.net:8443`
|
Access at `https://your-server.tailnet.ts.net:8443` (replace `tailnet` with your tailnet name, found in the Tailscale admin console)
|
||||||
|
|
||||||
### Install the CLI
|
### Install the CLI
|
||||||
|
|
||||||
|
|
@ -78,6 +79,8 @@ argocd repo add https://github.com/you/your-repo.git \
|
||||||
--password your-token
|
--password your-token
|
||||||
```
|
```
|
||||||
|
|
||||||
|
For BlumeOps, the git server is [[forgejo]] at `ssh://forgejo@forge.ops.eblu.me:2222`.
|
||||||
|
|
||||||
## Step 4: Create Your First Application
|
## Step 4: Create Your First Application
|
||||||
|
|
||||||
Create a directory in your repo:
|
Create a directory in your repo:
|
||||||
|
|
@ -173,11 +176,11 @@ spec:
|
||||||
server: https://kubernetes.default.svc
|
server: https://kubernetes.default.svc
|
||||||
namespace: argocd
|
namespace: argocd
|
||||||
syncPolicy:
|
syncPolicy:
|
||||||
automated:
|
syncOptions:
|
||||||
prune: true
|
- CreateNamespace=true
|
||||||
```
|
```
|
||||||
|
|
||||||
Now adding a new application is just creating a YAML file.
|
Now adding a new application is just creating a YAML file. BlumeOps syncs the `apps` Application manually — run `argocd app sync apps` after adding new Application YAMLs.
|
||||||
|
|
||||||
## Step 7: Configure Sync Policies
|
## Step 7: Configure Sync Policies
|
||||||
|
|
||||||
|
|
@ -188,7 +191,7 @@ Now adding a new application is just creating a YAML file.
|
||||||
| Auto prune | Remove resources deleted from git |
|
| Auto prune | Remove resources deleted from git |
|
||||||
| Self heal | Revert manual kubectl changes |
|
| Self heal | Revert manual kubectl changes |
|
||||||
|
|
||||||
BlumeOps uses manual sync for workloads, auto sync only for the `apps` Application itself.
|
BlumeOps uses manual sync for all applications, including the root `apps` Application.
|
||||||
|
|
||||||
## What You Now Have
|
## What You Now Have
|
||||||
|
|
||||||
|
|
@ -203,7 +206,7 @@ BlumeOps uses manual sync for workloads, auto sync only for the `apps` Applicati
|
||||||
- Add more applications to your repo
|
- Add more applications to your repo
|
||||||
- Set up notifications for sync failures
|
- Set up notifications for sync failures
|
||||||
|
|
||||||
## BluemeOps Specifics
|
## BlumeOps Specifics
|
||||||
|
|
||||||
BlumeOps' ArgoCD configuration includes:
|
BlumeOps' ArgoCD configuration includes:
|
||||||
- SSH connection to [[forgejo]] git server
|
- SSH connection to [[forgejo]] git server
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue