What problem does it solve?
Onboarding a new tenant into a shared Flux-based GitOps platform is easy to get wrong because it spans two repositories, multiple Kubernetes policies, secret delivery, traffic exposure, and signed artifact trust. This Skill helps you avoid the common failure modes that leave a tenant deployed but unreachable, rejected by admission, or unable to read its secrets.
Core Features & Use Cases
- Tenant repo guidance: Scaffolds the
deploy/ manifests for workloads, services, routes, pod disruption budgets, network policy, secrets, and optional database resources.
- Platform registration support: Describes the namespace, service account, RBAC, secret store, image-pull secret, and Flux sync resources needed to make a tenant live.
- Debugging and review: Helps diagnose onboarding issues such as seccomp violations, missing allow policies, incorrect secret-store scope, gateway attachment mistakes, and unsigned or unverified OCI artifacts.
- Use Case: A platform engineer can use this Skill to review a tenant onboarding PR end to end and confirm that the app will reconcile successfully after merge.
Quick Start
Use the gitops-tenant-onboarding skill to review a new tenant repository and its platform registration so I can check the manifests, policies, secrets, and Flux sync setup for readiness.