gitops-platform-bootstrap

Design Git repository structure and Argo CD architecture for GPU research platforms.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill gitops-platform-bootstrap-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-platform-bootstrap
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/gpu-research-platform/skills/gitops-platform-bootstrap
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill gitops-platform-bootstrap-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Platform teams running GPU research workloads on Kubernetes need every add-on and tenant environment declared in Git and continuously reconciled, instead of hand-applied kubectl changes that drift, race during bootstrap, and bypass review. ## Core Features & Use Cases - App-of-apps bootstrap: Stand up a root Argo CD Application that fans out to platform add-ons (GPU operator, DCGM monitoring, KEDA, JupyterHub, model serving) from a single repo. - ApplicationSet tenant vending: Generate one Application per folder under tenants/ so onboarding a researcher is merging a PR, with prune-based deprovisioning. - Sync-wave ordering and secrets strategy: Order CRDs, GPU operator, monitoring, and workloads with sync waves, and choose between Sealed Secrets, SOPS, and External Secrets Operator. - Use Case: On a fresh Lambda-managed Kubernetes cluster, install Argo CD, apply the root app, and have the full GPU platform plus per-researcher namespaces reconcile from Git with drift self-healing. ## Quick Start Ask the agent to design an Argo CD app-of-apps bootstrap repo with sync waves and an ApplicationSet that vends one namespace per tenant folder for your GPU cluster.

Frequently Asked Questions about gitops-platform-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a Kubernetes cluster with Argo CD app-of-apps?

Install Argo CD via Helm, then apply a single root Application pointing at a folder of child Application or ApplicationSet manifests. Syncing the root fans out to all platform add-ons, and automated sync with prune and selfHeal keeps the cluster reconciled to Git.

How do I vend one namespace per tenant with Argo CD ApplicationSet?

Use an ApplicationSet with a Git directory generator over a tenants/* folder path. Each folder generates an Application targeting a namespace named after the folder, so onboarding a tenant is merging a folder and deleting it deprovisions via prune.

Sealed Secrets vs SOPS vs External Secrets Operator for GitOps?

Sealed Secrets encrypts to a cluster keypair with no external dependencies and fits Argo CD natively. External Secrets Operator syncs from Vault or a cloud secrets manager with automatic rotation. SOPS encrypts files with KMS or age keys but needs a plugin for Argo CD.

Why do GPU workloads stay Pending after an Argo CD bootstrap?

Workloads requesting GPUs synced before the GPU operator and device plugin finished, so nodes do not yet advertise nvidia.com/gpu. Fix ordering with sync-wave annotations so CRDs and the GPU operator become healthy before consumer workloads sync.

Should I use environment branches or folders for GitOps promotion?

Use folders and overlays, not environment branches. Environments live as per-cluster value overlays in one repo, and promotion is a pull request that changes an overlay, keeping history reviewable and avoiding branch drift.