Flisk Helm

---
name: flisk-helm
description: Use Flisk for the local loop while production stays on Helm, Argo CD, Flux, Kustomize or another deploy pipeline - wrap the service with `flisk resource` (scaffolded or bring-your-own), map service.json fields to chart values by hand, and keep `.autogenerated/` out of the chart. Use when a team already has a Helm chart or cluster workflow and asks how Flisk fits next to it. Flisk does not export Helm or Kubernetes manifests. To ship to a specific cloud host, use the matching flisk-deploy-* skill.
license: MIT
compatibility: Requires the flisk CLI for local work. Does not install, edit or replace Helm charts or cluster tooling.
metadata:
  author: flisk-sh
  version: "1.0"
---

# Flisk next to Helm and cluster tooling

Flisk owns the local loop on the developer's machine. Helm (or Argo CD, Flux, Kustomize) owns the cluster. They are not alternatives.

```text
Local:   flisk up shop        → containers on this machine, *.localhost URLs
Cluster: helm upgrade …       → Deployment and Service in Kubernetes
```

## Workflow

1. Leave the existing chart, values and pipeline untouched.
2. Give the service a local definition:
   - a scaffolded resource (`flisk resource api --type backend --stack shop --yes`), or
   - its existing Dockerfile as bring-your-own (`flisk resource api --type bring-your-own --dockerfile ./Dockerfile --stack shop --yes`).
3. Develop with `flisk up <stack>`.
4. Release as before (`helm upgrade`, an Argo CD sync, a Flux reconcile), from the same image or Dockerfile.
5. Carry shared facts (image name, port, health path) into the chart values by hand.

## Conceptual mapping (not a translation)

| Flisk `service.json` | Helm / cluster | Boundary |
| --- | --- | --- |
| `appName` | release or controller name | identity only |
| `appType` | Deployment, Job or CronJob | Flisk does not pick the controller |
| `port` | Service port | confirm container and Service ports |
| `healthCheckPath` | readiness or liveness probe | tune probes for the cluster |
| `dependsOn` | ordering, hooks, init containers | not a cluster startup contract |
| Traefik `*.localhost` route | Ingress or Gateway API | DNS, TLS and class live in the cluster |
| local Postgres | managed database or chart dependency | persistence and backups are production's |

## Guardrails

- Do not copy `.autogenerated/` into a chart; it is local Docker and Tilt output.
- Flisk has no command that exports Helm values or Kubernetes manifests. Do not generate cluster manifests from Flisk.
- Flisk does not set replicas, PVCs, IRSA, HPA, node selectors or ingress classes.
- If `helm install`, Compose or an existing Tilt setup already gives a working local environment, Flisk may not be needed; say so.
- Guides: [docs/with-helm.md](https://github.com/flisk-sh/flisk/blob/main/docs/with-helm.md) and [docs/scope.md](https://github.com/flisk-sh/flisk/blob/main/docs/scope.md).