ark-controller-development

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

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/agents-at-scale --skill ark-controller-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ark-controller-development
Source: https://github.com/remiverdiesen/agents-at-scale/tree/main/.claude/skills/ark-controller-development
Command: npx skills add https://github.com/remiverdiesen/agents-at-scale --skill ark-controller-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance for developers who modify the Ark Kubernetes operator, helping ensure CRD generation and Helm chart synchronization are correct and consistent.

Core Features & Use Cases

  • CRD generation guidance: Align Go type changes with CRD generation and Helm chart updates.
  • Operator development workflow: Clear steps from type changes to manifest syncing and validation.
  • Use Case: When updating api/v1alpha1/*_types.go, run manifests and build to keep CRDs in sync and Helm charts current.

Quick Start

Navigate to the Ark repository and follow the workflow to update types, run manifests, and build to validate changes. Commands:

  • cd ark
  • make manifests
  • make build

Frequently Asked Questions about ark-controller-development

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

FAQPage Schema
How do I sync CRD generation with Helm chart updates in a Kubernetes operator?

To sync CRD generation with Helm chart updates, modify the Go types in api/v1alpha1/*_types.go, then run make manifests to generate CRDs and make build to validate the Helm chart synchronization.

Why does my Kubernetes operator CRD not match the updated Go types?

CRD manifests may not match updated Go types if you skip manifest generation. Run make manifests from the ark directory to regenerate CRDs in config/crd/bases and sync them to dist/chart/templates/crd.

What is the correct workflow for updating Ark Kubernetes operator types?

The Ark Kubernetes operator workflow requires editing api/v1alpha1/*_types.go, running make manifests to generate CRDs, and executing make build to validate that manifest generation and Helm chart updates are synchronized.

Can I use make build alone to validate CRD changes in the Ark operator?

No, make build alone does not validate CRD changes fully. You must run make manifests first to generate CRDs from Go types, then run make build to validate the overall operator changes and Helm chart synchronization.

When do I need to update Helm chart templates for Kubernetes CRD generation?

You need to update Helm chart templates whenever you modify Go types in api/v1alpha1/*_types.go. Running make manifests regenerates CRDs and ensures they sync into dist/chart/templates/crd for the Helm chart.

What are the limitations of skipping make manifests during Kubernetes operator development?

Skipping make manifests during operator development leaves CRDs outdated and desynchronized from Helm charts, causing validation failures in config/crd/bases and dist/chart/templates/crd when running make build.