helm-chart-development

Create Helm umbrella charts with standardized templates and versioning for ODA Canvas.

53|68|Updated Jan 5, 2021

Search Tags:#rbac #kubernetes #helm #templating #dependency-management #oda-canvas #chart-development

Ready to run

npx skills add https://github.com/tmforum-oda/oda-canvas --skill helm-chart-development-tmforum-oda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: helm-chart-development
Source: https://github.com/tmforum-oda/oda-canvas/tree/main/skills/helm-chart-development
Command: npx skills add https://github.com/tmforum-oda/oda-canvas --skill helm-chart-development-tmforum-oda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helm chart development for the ODA Canvas ecosystem often lacks standardization, leading to inconsistent deployments and slow onboarding. This Skill provides a unified approach to building umbrella charts, sub-charts, templating helpers, values.yaml conventions, RBAC templates, Docker image construction, prerelease suffix versioning, and dependency management to streamline chart creation and maintenance.

Core Features & Use Cases

Umbrella chart architecture with charts/canvas-oda and local sub-chart conventions
Standardized _helpers.tpl patterns, values.yaml structure, and RBAC templates
Deterministic Docker image construction, prerelease suffix versioning, and dependency management to ensure reproducible releases
Use Case: when introducing a new operator, follow these conventions to ensure consistency across environments and teams.

Quick Start

Create a new Helm umbrella chart following the conventions described and implement the required templates and versioning strategy.

Frequently Asked Questions about helm-chart-development

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

FAQPage Schema

How do I structure an umbrella Helm chart with local and external sub-chart dependencies?▼

An umbrella Helm chart organizes local sub-charts under a charts directory and defines external dependencies in Chart.yaml. This structure ensures consistent deployments and reproducible dependency management across the ODA Canvas platform.

What conventions should I use for values.yaml and _helpers.tpl in Helm chart development?▼

Helm chart development requires standardized values.yaml structures for configuration and _helpers.tpl patterns for reusable template logic. Following these conventions ensures consistent templating practices and accelerates onboarding for new operators.

How does prerelease suffix versioning work for Docker images in Helm charts?▼

Prerelease suffix versioning tags Docker images with deterministic prerelease identifiers during construction. This approach guarantees reproducible releases by matching image versions precisely with the Chart.yaml versioning strategy.

Can I use this Helm chart development approach to standardize RBAC templates for Kubernetes operators?▼

Yes, this approach provides standardized RBAC templates specifically designed for Kubernetes operators within the ODA Canvas. Implementing these templates ensures consistent role-based access control across different environments and teams.

What is the best way to manage dependencies across multiple Helm charts in a Kubernetes ecosystem?▼

Managing dependencies across multiple Helm charts requires a documented Chart.yaml structure and consistent dependency management practices. This ensures reproducible workflows for chart validation and release across the entire ecosystem.

Why do I need standardized Helm chart conventions for ODA Canvas deployments?▼

Standardized Helm chart conventions solve the problem of inconsistent deployments and slow onboarding within the ODA Canvas ecosystem. They enforce documented structures, consistent templating, and reproducible workflows for chart validation and release.