docs: correct phantom companion-repo references (aws-eks/CDK → landing-zone)#68
Merged
Conversation
…g-zone) The README, CLAUDE, and architecture overview pointed at a non-existent `aws-eks` (CDK) repo as the provisioner and listed a non-existent `gke-gitops` catalog in the multi-cloud strategy. The real provisioner is `landing-zone` (OpenTofu/Terragrunt) — it deploys the cloud substrate + Cilium + ArgoCD and creates the App-of-Apps that points here — and the GitOps catalogs are eks-gitops + aks-gitops (there is no GKE catalog). - aws-eks (CDK) → landing-zone (OpenTofu/Terragrunt), incl. the mermaid node and the "deployed by CDK" / "set by CDK" prose. - Dropped gke-gitops from the multi-cloud-strategy lists. The `aws-eks-*-backups` strings in environments.md are left as-is — those are actual S3 bucket names matching the velero config, not repo references.
CI Results
All validations passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README/CLAUDE/architecture docs pointed at a non-existent aws-eks (CDK) repo as the provisioner and listed a non-existent gke-gitops catalog. The real provisioner is landing-zone (OpenTofu/Terragrunt) — it deploys the substrate + Cilium + ArgoCD and creates the App-of-Apps — and the GitOps catalogs are eks-gitops + aks-gitops (no GKE catalog).
aws-eks(CDK) →landing-zone(OpenTofu/Terragrunt), incl. the mermaid node + 'deployed by CDK' prose.gke-gitopsfrom the multi-cloud lists.The
aws-eks-*-backupsstrings in environments.md are left — those are real S3 bucket names (velero config), not repo refs.