gitops-knowledge

Generate Flux CD YAML manifests for CRDs from schema-aligned templates.

204|10|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/fluxcd/agent-skills --skill gitops-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-knowledge
Source: https://github.com/fluxcd/agent-skills/tree/main/skills/gitops-knowledge
Command: npx skills add https://github.com/fluxcd/agent-skills --skill gitops-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines access to Flux CD knowledge and YAML manifest generation for Flux CRDs, reducing guesswork and errors.

Core Features & Use Cases

  • Answers Flux CD conceptual questions with precise, schema-aligned YAML templates for CRDs like GitRepository, OCIRepository, Kustomization, HelmRelease, ResourceSet, and FluxInstance.
  • Generates validated YAML manifests that adhere to Flux OpenAPI schemas and reference materials from the repo's references.
  • Assists with repository structure, multi-tenancy, OCI-based delivery, drift detection, and preview environments.

Quick Start

Ask for Flux CRD guidance and receive ready-to-apply YAML manifests.

Frequently Asked Questions about gitops-knowledge

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

FAQPage Schema
How do I generate valid YAML manifests for Flux CD custom resources like GitRepository and Kustomization?

Generating valid YAML manifests for Flux CD resources like GitRepository and Kustomization requires schema-aligned templates with exact apiVersion and kind combinations. This provides ready-to-apply YAML adhering to Flux OpenAPI schemas, eliminating guesswork and validation errors.

What is the best way to structure Flux CD manifests for multi-tenant GitOps delivery?

Structuring Flux CD manifests for multi-tenant GitOps delivery involves specific patterns for tenant isolation and access control. This provides conceptual guidance and YAML examples for multi-tenancy configurations, ensuring safe and organized resource distribution across distinct tenant environments.

How does OCIRepository work for Flux CD OCI-based artifact delivery?

OCIRepository in Flux CD works by pulling artifacts from OCI registries instead of Git repositories. This enables OCI-based delivery patterns, allowing you to source Kubernetes manifests packaged as OCI images and apply them using Kustomization or HelmRelease resources.

Can I use Flux CD to manage Helm releases alongside Kustomization resources?

Yes, you can use Flux CD to manage Helm releases alongside Kustomization resources. The HelmRelease custom resource allows you to define and deploy Helm charts, while Kustomization handles plain YAML manifests, both managed seamlessly through a unified GitOps workflow.

Do I need a FluxInstance resource to bootstrap Flux CD in my cluster?

Bootstrapping Flux CD in a cluster involves initializing the core controllers and custom resource definitions. The FluxInstance resource provides a managed way to install and configure Flux itself, generating the necessary YAML manifests to initialize and maintain the GitOps automation toolkit.

Why does my Flux CD Kustomization manifest fail validation due to incorrect apiVersion or kind fields?

Flux CD Kustomization manifests fail validation when the apiVersion and kind fields do not match the exact specifications defined in the CRD schemas. Using schema-aligned templates ensures the generated YAML enforces correct apiVersion and kind combinations, preventing deployment validation errors.