multi-cloud no mcp
This commit is contained in:
@@ -37,7 +37,7 @@ Bootstrap a new cluster from scratch:
|
||||
|
||||
#### Prerequisites
|
||||
|
||||
1. **Kubernetes cluster running** (UpCloud or any K8s cluster)
|
||||
1. **Kubernetes cluster running** (UpCloud, AWS EKS, Azure AKS, GCP GKE, or any K8s cluster)
|
||||
2. **kubectl configured** with admin access
|
||||
3. **Repositories cloned** locally
|
||||
|
||||
@@ -54,11 +54,13 @@ kubectl get nodes
|
||||
git clone https://git.forteapps.net/Forte/launchpad
|
||||
cd launchpad
|
||||
|
||||
# 2. Set cluster name (optional)
|
||||
export CLUSTER_NAME="prod-cluster-01"
|
||||
# 2. Run bootstrap script with cluster target
|
||||
# Available clusters: upc-dev, upc-prod, aws-dev, aws-prod,
|
||||
# azure-dev, azure-prod, gcp-dev, gcp-prod
|
||||
./bootstrap.sh upc-dev
|
||||
|
||||
# 3. Run bootstrap script
|
||||
./bootstrap.sh
|
||||
# Cluster config is loaded from clusters/<cluster>.yaml
|
||||
# (cloudProvider, trustedIPs, domain, etc.)
|
||||
```
|
||||
|
||||
**What Happens:**
|
||||
@@ -1262,13 +1264,21 @@ spec:
|
||||
|
||||
### Backup Strategy
|
||||
|
||||
**Current State**: No automated backups
|
||||
**Current State**: Gitea daily backups to S3-compatible storage
|
||||
|
||||
**What Needs Backup**:
|
||||
- ❌ Cluster state (not backed up - recreate via GitOps)
|
||||
- ❌ Persistent volumes (currently not critical)
|
||||
- ✅ Git repositories (Gitea provides backup)
|
||||
- ⚠️ Secrets (sealed secrets in Git, unseal keys need safekeeping)
|
||||
**What Is Backed Up**:
|
||||
- ✅ Gitea repositories + database: Daily CronJob (`cluster-resources/gitea-backup-cronjob.yaml`) uploads to S3-compatible storage with 7-day retention
|
||||
- ✅ Git repositories: Full cluster config recoverable from Git
|
||||
- ⚠️ Secrets: Sealed secrets in Git; unseal keys need safekeeping
|
||||
|
||||
**What Is NOT Backed Up**:
|
||||
- ❌ Cluster state (recreate via GitOps)
|
||||
- ❌ Other persistent volumes (Prometheus, Loki, Tempo data)
|
||||
|
||||
**Per-cloud backup scripts** (manual restore helpers):
|
||||
- UpCloud/AWS: `scripts/gitea-backup.sh` / `scripts/gitea-backup-aws.sh` (MinIO CLI, S3-compatible)
|
||||
- Azure: `scripts/gitea-backup-azure.sh` (Azure CLI + Blob Storage)
|
||||
- GCP: `scripts/gitea-backup-gcp.sh` (gsutil + GCS)
|
||||
|
||||
### Cluster Rebuild
|
||||
|
||||
@@ -1370,6 +1380,9 @@ kubectl get pods -n argocd
|
||||
|
||||
```bash
|
||||
# UpCloud: Upgrade via control panel or CLI
|
||||
# AWS EKS: eksctl upgrade cluster / AWS Console
|
||||
# Azure AKS: az aks upgrade / Azure Portal
|
||||
# GCP GKE: gcloud container clusters upgrade / Cloud Console
|
||||
|
||||
# After upgrade, verify cluster
|
||||
kubectl version
|
||||
@@ -1507,18 +1520,35 @@ git push
|
||||
|
||||
### Multi-Cluster Setup
|
||||
|
||||
The repository supports multiple clusters via Kustomize overlays:
|
||||
The repository supports multiple clusters across multiple clouds via Kustomize overlays:
|
||||
|
||||
**Active clusters:**
|
||||
- **upc-dev** (default): `infra/overlays/upc-dev/` — uses base Applications as-is
|
||||
- **upc-prod**: `infra/overlays/upc-prod/` — patches value file paths from `upc-dev` to `upc-prod`
|
||||
|
||||
Each cluster has its own:
|
||||
- Root app-of-apps file: `_app-of-apps-upc-dev.yaml` / `_app-of-apps-upc-prod.yaml`
|
||||
- Cluster-specific Helm values: `infra/values/upc-dev/` / `infra/values/upc-prod/`
|
||||
- Sealed secrets: `secrets/upc-dev/` (others as needed)
|
||||
- Apps overlay: `apps/overlays/upc-dev/` / `apps/overlays/upc-prod/`
|
||||
**Cloud-ready templates (fill in `clusters/*.yaml` before use):**
|
||||
- **aws-dev** / **aws-prod**: AWS EKS with NLB, gp3 storage, AWS CUR pricing
|
||||
- **azure-dev** / **azure-prod**: Azure AKS with Standard LB, managed-csi-premium storage
|
||||
- **gcp-dev** / **gcp-prod**: GCP GKE with L4 LB, premium-rwo storage
|
||||
|
||||
To add a new cluster, create a new overlay directory (e.g., `infra/overlays/upc-staging/`) with patches that swap the value file paths.
|
||||
Each cluster has its own:
|
||||
- Root app-of-apps: `_app-of-apps-{cluster}.yaml`
|
||||
- Cluster config: `clusters/{cluster}.yaml` (domain, trustedIPs, cloudProvider)
|
||||
- Kustomize overlay: `infra/overlays/{cluster}/kustomization.yaml`
|
||||
- Helm value overrides: `infra/values/{cluster}/` (traefik, gitea, opencost)
|
||||
- Sealed secrets: `secrets/{cluster}/` (as needed)
|
||||
- Apps overlay: `apps/overlays/{cluster}/`
|
||||
|
||||
Cloud-specific values handled per-cluster:
|
||||
|
||||
| Concern | UpCloud | AWS EKS | Azure AKS | GCP GKE |
|
||||
|---------|---------|---------|-----------|---------|
|
||||
| **Storage class** | `upcloud-block-storage-maxiops` | `gp3` | `managed-csi-premium` | `premium-rwo` |
|
||||
| **Load balancer** | UpCloud LB + ProxyProtocol v2 | NLB + ProxyProtocol v2 | Standard LB + `externalTrafficPolicy: Local` | L4 passthrough NLB |
|
||||
| **Cost monitoring** | Custom pricing | AWS CUR | Azure Billing API | GCP Cloud Billing |
|
||||
| **Backup storage** | UpCloud S3-compat | AWS S3 (native) | Azure Blob Storage | GCS |
|
||||
|
||||
To add a new cluster, create a new overlay directory (e.g., `infra/overlays/aws-staging/`) with patches that swap the value file paths, and a matching `clusters/aws-staging.yaml`.
|
||||
|
||||
### Blue-Green Deployments
|
||||
|
||||
@@ -1661,6 +1691,6 @@ echo "Remember to delete: $SECRET_FILE"
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2026-03-16
|
||||
**Last Updated**: 2026-04-22
|
||||
**Maintained By**: Platform Team
|
||||
**Emergency Contact**: #platform-support on Slack
|
||||
|
||||
Reference in New Issue
Block a user