deploy-app

Orchestrates Kubernetes deployments via Helm charts, GitOps config, validation, and monitoring checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the manual, error-prone work of deploying a new Kubernetes application by guiding you through chart selection, GitOps configuration, validation, and proof of readiness with networking and monitoring checks.

Core Features & Use Cases

  • Research and chart selection: Compares native Helm charts versus app-template approaches using kubesearch and Helm chart discovery.
  • Deterministic GitOps setup: Creates an isolated worktree, updates versions.env, namespace configuration, Helm chart inputs, values files, and registers the app in kustomization.yaml.
  • Dev verification with guardrails: Performs direct dev-cluster testing (bypassing Flux temporarily) including pod readiness, network-policy verification via Hubble, and monitoring validation (ServiceMonitor/alerts).
  • Production-ready PR workflow: Uninstalls the direct Helm deployment, runs Flux reconciliation validation, then commits and opens the PR.

Quick Start

Use the deploy-app skill to orchestrate end-to-end deployment of a new application by creating an isolated worktree, configuring Helm inputs and values, validating manifests, testing on the dev cluster with Hubble and monitoring checks, and finally reconciling via Flux before opening the PR.

Frequently Asked Questions about deploy-app

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

FAQPage Schema
How do I deploy a Helm application to Kubernetes using FluxCD GitOps?

To deploy a Helm application using FluxCD GitOps, you configure HelmRelease inputs, update versions.env and helm-charts.yaml, validate manifests, test on a dev cluster, and reconcile via Flux before opening a PR.

What is the best way to validate Kubernetes network policies before promoting a Helm release?

Validating Kubernetes network policies before promoting a Helm release involves testing direct deployments on a dev cluster and running Hubble checks to verify traffic readiness before Flux GitOps promotion.

How do I set up ServiceMonitor and PrometheusRule resources for a new Helm chart?

Setting up ServiceMonitor and PrometheusRule resources for a Helm chart requires adding monitoring configurations to your values files, validating them during dev cluster testing, and registering them in your kustomization.yaml.

Does this Kubernetes deployment workflow require a git worktree setup?

Yes, this Kubernetes deployment workflow requires an isolated git worktree setup to safely modify versions.env, namespace configurations, and kustomization registrations before opening a pull request.

Can I test Helm releases on a dev cluster before applying FluxCD reconciliation?

Yes, you can test Helm releases on a dev cluster by running direct helm install commands to bypass Flux, verifying pod readiness and monitoring checks, then uninstalling before triggering Flux reconcile validation.

Why does my Flux reconcile validation fail when deploying Helm charts?

Flux reconcile validation fails when deploying Helm charts if manifests do not pass k8s:validate or renovate:validate checks, or if the cluster has not reached convergence during the GitOps promotion phase.