gitops-tenant-onboarding

Review tenant onboarding manifests for Flux-based GitOps platform readiness.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/devantler-tech/agent-plugins --skill gitops-tenant-onboarding-devantler-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-tenant-onboarding
Source: https://github.com/devantler-tech/agent-plugins/tree/main/plugins/gitops-kubernetes/skills/gitops-tenant-onboarding
Command: npx skills add https://github.com/devantler-tech/agent-plugins --skill gitops-tenant-onboarding-devantler-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about gitops-tenant-onboarding

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

FAQPage Schema
How do I onboard a new tenant to a Flux-based GitOps platform?

Tenant onboarding in Flux requires scaffolding deploy manifests, platform registration, namespaced secret stores, Gateway API exposure, and trust verification for published OCI artifacts.

Why are my Flux tenant pods rejected by Kubernetes admission during onboarding?

Admission rejections during Flux tenant onboarding often stem from seccomp violations, missing Kyverno allow policies, or incorrect PodSecurity standards that block workload reconciliation.

What manifests do I need to expose a tenant app using Gateway API in Kubernetes?

Exposing a tenant app via Gateway API requires deploy manifests for workloads, services, routes, network policies, and correct gateway attachment to ensure the application becomes reachable.

How do I deliver External Secrets to a multi-tenant Flux environment safely?

Delivering External Secrets in multi-tenant Flux requires namespaced secret stores and proper RBAC configuration so each tenant can securely read its required secrets.

Can I use signed OCI artifacts for Flux tenant resources?

Yes, multi-tenant Flux onboarding supports and verifies signed OCI artifacts to ensure trust verification for published tenant artifacts before they reconcile successfully.

What is the best way to debug a Flux tenant that is deployed but unreachable?

Debugging an unreachable Flux tenant involves reviewing gateway attachment mistakes, incorrect secret-store scope, missing allow policies, and unsigned OCI artifacts that prevent successful reconciliation.