Skip to content

Commit 47a885a

Browse files
committed
add architecture overview svg to docs
1 parent 3530c10 commit 47a885a

2 files changed

Lines changed: 22 additions & 14 deletions

File tree

docs/modules/demos/images/argo-cd-git-ops/architecture-overview.svg

Lines changed: 4 additions & 0 deletions
Loading

docs/modules/demos/pages/argo-cd-git-ops.adoc

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,14 @@ All products and manifests are synced and deployed via ArgoCD (except ArgoCD its
1414

1515
The key points to show are:
1616

17-
* GitOps: How to deploy my changes from a Git repository to my cluster
18-
* Secrets: How to safely deploy credentials, access keys and store them in a Git repository
19-
* Although not included in this Demo, it assumes / tries to imitate a possible
20-
multicluster setup for development, staging and production.
17+
* GitOps: How to deploy changes from a Git repository to my cluster?
18+
* Secrets: How to safely store and deploy credentials, access keys from a Git repository?
2119
* Interaction with Stackable products (e.g. Airflow and DAGs via gitsync)
2220
21+
ArgoCD and other deployed products and dependencies are illustrated in the following diagram:
22+
23+
image::argo-cd-git-ops/architecture-overview.svg[]
24+
2325
Install this demo on an existing Kubernetes cluster:
2426

2527
[source,console]
@@ -44,16 +46,18 @@ To run this demo, your system needs at least:
4446

4547
This demo consists of multiple parts:
4648

47-
* Bootstrapping via `stackablectl`
48-
** Install {argo-cd}[Argo CD] via `stackablectl`.
49-
* After the initial bootstrapping, ArgoCD takes over the deployment:
50-
** Install a {sealed-secrets}[Sealed Secrets] controller to handle sensitive data like credentials or secret keys.
51-
** Install all Stackable operators using an `ApplicationSet`.
52-
** Spin up requirements like Minio and Postgres as `Application`.
53-
** Deploy Stackable Airflow manifests in their respective `Projects`.
54-
** DAGs are synced via Airflow gitsync, not ArgoCD.
55-
** Airflow uses the Kubernetes executor and write its logs to S3 / Minio.
56-
** DAGs can be started manually in the Airflow webserver UI
49+
* Bootstrapping via `stackablectl`:
50+
** Install {argo-cd}[Argo CD] via `stackablectl`
51+
* Deploy components via ArgoCD:
52+
** Install a {sealed-secrets}[Sealed Secrets] controller to handle sensitive data like credentials or secret keys
53+
** Install all Stackable operators using an `ApplicationSet`
54+
** Install requirements like Minio and Postgres as `Application`
55+
** Deploy Stackable Airflow manifests into their respective `Projects`
56+
* Inspect ArgoCD UI
57+
* Inspect Airflow and start DAGs
58+
** Checkout Airflow UI and synced DAGs (the DAGs are synced via gitsync, not ArgoCD)
59+
** Start a DAG and inspect the logs written to S3 / Minio by the Kubernetes executor
60+
* Optional: Inspect Minio UI for logs
5761

5862
TODO: arch overview image
5963

0 commit comments

Comments
 (0)