github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-05-19 07:16:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add an additonal considerations slide for ArgoCD

Browse Source
This commit is contained in:
Anton Weiss
2022-01-30 16:48:04 +02:00
committed by Jérôme Petazzoni
parent e97c93e451
commit ce13afa0d4
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
slides/k8s/argocd.md
View File

@@ -4,7 +4,7 @@
- These YAML files can and should be stored in source control - specifically - Git
- YAML manifests from Git can then be used to continuously update our cluster configuraition
- YAML manifests from Git can then be used to continuously update our cluster configuration
- When this process is automated - it is now called "GitOps"
@@ -444,4 +444,16 @@ Change the ~/container.training/k8s/argocd_app.yaml to deploy `rng`, `hasher`, `
Apply the application resource for each.
]
]
---
## Additional Considerations for Using ArgoCD
- When running in production ArgoCD should be integrated with an SSO (Single-Sign On) provider - either with the bundled [Dex](https://argo-cd-docs.readthedocs.io/en/latest/operator-manual/sso/#dex) instance or with an existing OIDC provider (Okta, Auth0, etc)
- A single ArgoCD instance can manage multiple clusters
- Alternatively one can have an ArgoCD per cluster
- ArgoCD can be complemented with [Argo Rollouts](https://argoproj.github.io/argo-rollouts/) for advanced rollout control