flux-gitops

Add Helm releases to Flux ResourceSet platforms and debug reconciliation failures.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill flux-gitops-david-driscoll
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flux-gitops
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/flux-gitops
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill flux-gitops-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flux GitOps users often struggle to correctly onboard new Helm releases into a ResourceSet-driven platform and to diagnose reconciliation failures like missing values or stalled syncs.

Core Features & Use Cases

  • Centralized HelmRelease onboarding with ResourceSets: Adds new charts by updating platform inputs and values registration so HelmReleases render consistently across namespaces.
  • Version pinning with Flux substitution: Uses versions.env variables (and Renovate annotations) to keep chart versions managed declaratively.
  • Dependency-aware rollout and troubleshooting: Clarifies HelmRelease dependsOn vs ResourceSet dependsOn and provides a practical debugging workflow for common Flux symptoms.
  • OCI vs HTTP Helm repository support: Handles OCI chart sources by recognizing oci:// prefixes and setting type: oci for HelmRepository.

Quick Start

Ask the skill to walk you through adding a new Helm release named my-app from a given chart URL into the apps namespace, including how to register its values and what to check if it gets stuck.

Frequently Asked Questions about flux-gitops

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

FAQPage Schema
How do I add a new Helm release to a Flux ResourceSet?▼

Adding a Helm release to a Flux ResourceSet involves editing helm-charts.yaml inputs, creating charts/<release-name>.yaml values files, and registering them via kustomization.yaml configMapGenerator for consistent namespace rendering.

How does Flux handle OCI chart URLs in a HelmRepository?▼

Flux handles OCI chart URLs by recognizing the oci:// prefix and configuring the HelmRepository with type: oci to ensure proper chart synchronization.

What is the difference between HelmRelease dependsOn and ResourceSet dependsOn?▼

HelmRelease dependsOn governs dependencies between individual chart releases, whereas ResourceSet dependsOn controls the synchronization order at the broader ResourceSet layer for dependency-aware GitOps rollouts.

Why is my Flux GitOps HelmRelease not reconciling?▼

Flux GitOps reconciliation failures often stem from missing values files, incorrect versions.env variable substitution in resourcesTemplate inputs, or stalled syncs across the HelmRelease and ResourceSet layers.

How do I pin Helm chart versions declaratively with Flux?▼

You pin Helm chart versions declaratively with Flux by using versions.env variables for substitution within resourcesTemplate inputs, often combined with Renovate annotations to keep chart versions managed.