docs
This commit is contained in:
20
README.md
20
README.md
@@ -146,12 +146,12 @@ This repository contains the complete GitOps configuration for our Kubernetes cl
|
||||
|------------|---------|-----------|-----------|
|
||||
| **[launchpad](https://git.forteapps.net/Forte/launchpad)** (this repo) | ArgoCD Applications, cluster resources | Platform / DevOps engineers | ✅ Often |
|
||||
| **[forte-helm](https://git.forteapps.net/Forte/forte-helm)** | Generic Helm chart templates | Platform engineers | ❌ Rarely |
|
||||
| **[helm-values](ssh://git@git.forteapps.net:2222/Forte/helm-prod-values.git)** | App-specific configuration & versions | Developers / CI pipelines | ✅ Sometimes |
|
||||
| **[helm-prod-values](ssh://git@git.forteapps.net:2222/Forte/helm-prod-values.git)** | App-specific configuration & versions | Developers / CI pipelines | ✅ Sometimes |
|
||||
|
||||
### GitOps Workflow
|
||||
|
||||
```
|
||||
Developer commits code → CI/CD builds image → Updates helm-values → ArgoCD syncs → Deployed to cluster
|
||||
Developer commits code → CI/CD builds image → Updates helm-prod-values → ArgoCD syncs → Deployed to cluster
|
||||
```
|
||||
|
||||
**Learn more**: [GitOps Architecture - GitOps Workflow](docs/GITOPS-ARCHITECTURE.md#gitops-workflow)
|
||||
@@ -166,7 +166,7 @@ Developer commits code → CI/CD builds image → Updates helm-values → ArgoCD
|
||||
|
||||
**Quick version**:
|
||||
1. Create `apps/myapp.yaml` (ArgoCD Application manifest)
|
||||
2. Create `helm-values/myapp/values.yaml` (configuration)
|
||||
2. Create `helm-prod-values/myapp/values.yaml` (configuration)
|
||||
3. Create sealed secrets if needed
|
||||
4. Commit and push - ArgoCD auto-syncs!
|
||||
|
||||
@@ -175,8 +175,8 @@ Developer commits code → CI/CD builds image → Updates helm-values → ArgoCD
|
||||
**See detailed guide**: [Developer Guide - Updating an Existing Application](docs/DEVELOPER-GUIDE.md#updating-an-existing-application)
|
||||
|
||||
**Quick version**:
|
||||
- **Update code**: Push to app repo → CI/CD updates image tag in helm-values
|
||||
- **Update config**: Edit `helm-values/myapp/values.yaml` → commit → push
|
||||
- **Update code**: Push to app repo → CI/CD updates image tag in helm-prod-values
|
||||
- **Update config**: Edit `helm-prod-values/myapp/values.yaml` → commit → push
|
||||
|
||||
### Manage Secrets
|
||||
|
||||
@@ -204,7 +204,7 @@ git push
|
||||
|
||||
**Quick version**:
|
||||
```yaml
|
||||
# In helm-values/myapp/values.yaml
|
||||
# In helm-prod-values/myapp/values.yaml
|
||||
|
||||
# Token-based auth (simple)
|
||||
auth:
|
||||
@@ -366,7 +366,7 @@ kubectl patch application myapp -n argocd \
|
||||
### Multi-Source Pattern
|
||||
Applications reference both:
|
||||
1. **Helm charts** from `forte-helm` (templates)
|
||||
2. **Values** from `helm-values` (configuration)
|
||||
2. **Values** from `helm-prod-values` (configuration)
|
||||
|
||||
This separates reusable templates from environment-specific config.
|
||||
|
||||
@@ -435,7 +435,7 @@ Applications deploy in order using `argocd.argoproj.io/sync-wave`:
|
||||
### Adding a New Application
|
||||
1. Read [Developer Guide - Deploying Your First Application](docs/DEVELOPER-GUIDE.md#deploying-your-first-application)
|
||||
2. Create ArgoCD Application manifest in `apps/`
|
||||
3. Create Helm values in `helm-values/`
|
||||
3. Create Helm values in `helm-prod-values/`
|
||||
4. Create sealed secrets if needed
|
||||
5. Commit and push - ArgoCD handles the rest!
|
||||
|
||||
@@ -485,8 +485,8 @@ Documentation lives in `docs/`. To update:
|
||||
- [Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets)
|
||||
|
||||
### Related Repositories
|
||||
- [forte-helm](https://github.com/fortedigital/forte-helm) - Helm chart templates
|
||||
- [helm-values](git@github.com:fortedigital/helm-values.git) - Application values
|
||||
- [forte-helm](https://git.forteapps.net/Forte/forte-helm) - Helm chart templates
|
||||
- [helm-prod-values](git@github.com:fortedigital/helm-prod-values.git) - Application values
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user