spec: invert platform GitOps to per-cluster ArgoCD pull model - #186
Draft
markturansky wants to merge 1 commit into
Draft
spec: invert platform GitOps to per-cluster ArgoCD pull model#186markturansky wants to merge 1 commit into
markturansky wants to merge 1 commit into
Conversation
Rework the global architecture spec so ArgoCD runs on every cluster and each cluster self-reconciles its own path from the central hypershell-gitops repo, replacing the hub-push model where a Cloud Hub ArgoCD held remote kubeconfigs and reconciled into its ManagedClusters. Scope is the platform GitOps layer only. The control-plane tenant reconciliation (runtime push from the Cloud Hub PostgreSQL via gRPC) is preserved and now explicitly documented as a distinct plane. - Overview: state pull-not-push; add two-plane callout - Topology diagram: central repo node, ArgoCD on all tiers, pull arrows - Tier 1/2/3: ArgoCD self-reconciles own path; Tier 2 no longer targets MCs - Data Flows: new Platform GitOps Pull Flow sequence + key points - Tooling Stack + Design Decisions: ArgoCD-on-every-cluster pull model - GitOps Repository Structure: rewrite to real hypershell-gitops layout (bases/ + per-cluster clusters/<name>/ entrypoints, bin/bootstrap) Refs: HYPERSHELL-6 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Reworks
specs/platform/global-architecture.spec.mdto invert the platform GitOps deployment model from hub-push to per-cluster pull.hypershell-gitopsrepo and applying locally. No cluster stores another's kubeconfig; no hub pushes outward.This brings the spec in line with the real
hypershell-gitopsrepo, which already uses a per-cluster layout (clusters/{global,hysh-ibm-01,uat}/+bin/bootstrap).Scope
Platform GitOps layer only. The control-plane tenant reconciliation (runtime push from the Cloud Hub PostgreSQL via gRPC watch) is unchanged and now explicitly documented as a distinct plane so the two aren't conflated.
Changes
hypershell-gitopslayout (bases/+ per-clusterclusters/<name>/entrypoints)Jira
HYPERSHELL-6
🤖 Generated with Claude Code