app-template

Generate Kubernetes HelmRelease values using the bjw-s/app-template chart.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploying a containerized application to Kubernetes usually requires a dedicated Helm chart, but many images only provide raw containers and example manifests. This Skill helps you use the bjw-s/app-template Helm chart to generate the common Kubernetes resources you need (controllers, services, ingress, and storage) in a consistent, GitOps-friendly way.

Core Features & Use Cases

  • Generic Helm deployment: Deploy container images that do not have an official Helm chart by expressing the app in app-template values rather than writing a custom chart.
  • Flux HelmRelease-ready configuration: Produce HelmRelease manifests/values that fit Flux GitOps workflows (including typical ResourceSet-based setups).
  • Multi-container pod patterns: Configure sidecars and init containers using app-template’s structured values model, including dependency ordering (e.g., main → sidecar → helper containers).
  • Kubernetes resource coverage: Set up Services, Ingress, and Persistent storage (PVC, emptyDir, NFS, etc.) using the chart’s standard fields.
  • Security posture for restricted namespaces: Apply the full PodSecurity restricted profile requirements at pod/container level when deploying into restricted namespaces.

Quick Start

Tell the AI to generate app-template values.yaml for your app image repository and tag, including the container port, the service port mapping, and whether you need ingress and persistence.

Frequently Asked Questions about app-template

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

FAQPage Schema
How do I deploy a container image to Kubernetes without a dedicated Helm chart?

You deploy a container image without a Helm chart by expressing the app in bjw-s/app-template values, which generates the required Kubernetes controllers, services, ingress, and storage resources without writing a custom chart.

Can I create Flux GitOps HelmRelease configurations using app-template values?

Yes, you can create Flux GitOps HelmRelease configurations using app-template values, which produce Flux-compatible HelmRelease manifests and typical ResourceSet-based setups for GitOps deployment workflows.

How do I configure sidecars and init containers in a multi-container pod using app-template?

You configure sidecars and init containers by using app-template's structured values model to define multi-container pods, including dependency ordering like main, sidecar, and helper containers, without writing custom manifests.

Does deploying to a restricted namespace require specific PodSecurity settings in app-template?

Yes, deploying to a restricted namespace requires applying the full PodSecurity restricted profile requirements at the pod and container level, including the required securityContext fields in your app-template values.

What's the best way to wire services and ingress for an app-template Kubernetes deployment?

The best way to wire services and ingress is by using the chart's standard fields, ensuring correct service.controller wiring and port identifiers are set in your app-template values to route traffic properly.