skills.rest
COLDTURNIP
COLDTURNIPCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sync-crd-helm

Synchronize CRD changes from API source into Helm templates and manifests.

Updated Jan 19, 2026
Search Tags:#automation#deployment#synchronization#kubernetes#helm#crd#longhorn
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill sync-crd-helm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-crd-helm
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/sync-crd-helm
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill sync-crd-helm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires make, git, bash, grep, cp, mkdir.

What problem does it solve?

This Skill automates the synchronization of CRD changes from the API source (longhorn-manager) to the Helm chart and deployment manifests, ensuring consistency across the deployment pipeline.

Core Features & Use Cases

  • CRD propagation: Generates and copies CRD YAMLs from the API source into the Helm chart templates.
  • Manifest regeneration: Updates final manifests after CRD changes to reflect the new schema.
  • Release readiness: Supports release prep by aligning API changes with packaging files and deployment manifests.

Quick Start

bash .opencode/skills/sync-crd-helm/sync_crd_helm.sh

Frequently Asked Questions about sync-crd-helm

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

FAQPage Schema
How do I synchronize CRD changes from longhorn-manager to Helm chart templates?▼

CRD synchronization is automated by a three-stage Bash workflow that generates CRD YAMLs from the API source, copies them into Helm templates, and regenerates deployment manifests to maintain consistency across the pipeline.

What is the best way to automate CRD propagation for Longhorn release preparation?▼

Automating CRD propagation for Longhorn release prep requires a Make and Bash workflow that aligns API schema changes with packaging files and deployment manifests across repo/longhorn-manager and repo/longhorn.

Do I need Make and Git to run the CRD and Helm chart synchronization workflow?▼

Yes, the CRD and Helm chart synchronization workflow requires Make, Git, Bash, grep, cp, and mkdir to execute its three-stage process of generating, copying, and regenerating YAML manifests.

How does manifest regeneration work after updating Kubernetes CRD schemas?▼

Manifest regeneration updates final deployment manifests after CRD changes by reflecting the new schema from the API source, ensuring the deployment pipeline remains consistent with the updated Helm chart templates.

When do I need to update CRDs in Helm charts for Kubernetes deployments?▼

You need to update CRDs in Helm charts during Longhorn release prep or ongoing development workflows when API changes in longhorn-manager must be reflected across deployment manifests and packaging files.

Related Skills

Explore More Software Engineering Skills→
COLDTURNIPCOLDTURNIP

longhorn-build-system

Auto-generates Make targets from scripts/ files using Dapper containers in Longhorn repos.

Community
Advanced
remiverdiesenremiverdiesen
6

ark-controller-development

Guide CRD generation and Helm chart synchronization for Ark Kubernetes operator changes.

Community
Advanced
bacocobacoco
2

cortex

Trace file changes and commits to generate Cortex session memory files.

Community
Advanced
CatsofsufferingCatsofsuffering
5

infrastructure

Guide engineers in designing Kubernetes, Helm, Kustomize, and GitOps infrastructure.

Community
Advanced