Jean-Gabriel Gill-Couture
99e661ce4d
All checks were successful
Run Check Script / check (pull_request) Successful in 2m44s
Chapter 3 scaffolding. Chart layout mirrors the CloudNativePG convention after reviewing the CRD-in-chart vs CRD-as-hook tradeoff: CRDs live inside templates/ (so helm upgrade re-applies schema changes) with helm.sh/resource-policy: keep so helm uninstall never deletes them. Chart publication target is hub.nationtech.io. CRD yaml is generated at chart-release time by a new `iot-operator-v0 gen-chart-crd` subcommand reading Deployment::crd() — the runtime install path remains the typed Score; only the chart deliverable uses generated yaml. Wrapped with the helm conditional + annotations by templates/crds.yaml via .Files.Get so the generated yaml stays pure. Install / upgrade / uninstall-preserves-CRD validated against a scratch k3d cluster; the operator pod naturally stays pending because the hub.nationtech.io image hasn't been published yet.
18 lines
385 B
YAML
18 lines
385 B
YAML
apiVersion: v2
|
|
name: iot-operator-v0
|
|
description: NationTech IoT operator — Deployment CRD → NATS JetStream KV fleet reconciler.
|
|
type: application
|
|
version: 0.1.0
|
|
appVersion: "0.1.0"
|
|
home: https://nationtech.io
|
|
sources:
|
|
- https://git.nationtech.io/Nationtech/harmony
|
|
keywords:
|
|
- iot
|
|
- nats
|
|
- operator
|
|
- fleet
|
|
maintainers:
|
|
- name: NationTech
|
|
email: dev@nationtech.io
|