helm-chart-generator

Generate Helm charts and Kubernetes manifests, then open kube-manifests PRs via MCP.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill helm-chart-generator-razorpay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: helm-chart-generator
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/helm-chart-generator
Command: npx skills add https://github.com/razorpay/trino-gateway --skill helm-chart-generator-razorpay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the generation of production-ready Helm charts and Kubernetes manifests for Razorpay services and streamlines PR creation on kube-manifests via MCP, eliminating manual chart crafting and git workflows.

Core Features & Use Cases

  • Generates Helm charts and Kubernetes manifests for Razorpay services.
  • Opens kube-manifests PRs through MCP tools, enabling server-side chart management without local git commands.
  • Supports onboarding new services, adding components (workers, cronjobs, HPA, PDB, KEDA, ConfigMap), onboarding UPI gateways, and previewing chart files.
  • Use case: Onboard a new service to Kubernetes by generating charts for web deployments and automatically creating PRs to kube-manifests.

Quick Start

Describe your service and deployment requirements and the skill will generate Helm charts and create kube-manifests PRs via MCP.

Frequently Asked Questions about helm-chart-generator

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

FAQPage Schema
How do I generate Helm charts for Kubernetes onboarding without manual git commands?

You can generate production-ready Helm charts and Kubernetes manifests by providing service details like service_name and environment, then automatically opening kube-manifests PRs through MCP without local git commands.

Can I create Kubernetes manifests for both stage and prod environments?

Yes, you can configure single-env or multi-env Kubernetes deployments across stage and prod environments by specifying the target environment in your MCP routing inputs.

What Kubernetes components can I add when generating Helm charts?

You can generate Helm charts for web deployments, workers, cronjobs, HPA, PDB, KEDA, and ConfigMaps by specifying the service_type and optional parameters like ports and replicas.

What inputs do I need to onboard a new service to Kubernetes via MCP?

Required inputs for onboarding a service include service_name, service_type, namespace, image, and environment, along with optional ports, replicas, and ingress settings routed via MCP.

Does this approach support opening pull requests directly to kube-manifests?

Yes, it opens kube-manifests PRs through MCP tools, enabling server-side Helm chart management and eliminating manual chart crafting and local git workflows.

What is the best way to automate Helm chart creation for new workers and cronjobs?

Automate Helm chart creation by describing your service and deployment requirements, which generates manifests for workers or cronjobs and creates kube-manifests PRs via MCP.