kadet-hub
Tags
A tag is a claim by the generator's author. The maintainer checks it in review against this page; for kubernetes, helm and terraform the evidence named below can be checked in the manifest and the compiled output.
CI/CD ci
Build and delivery pipelines.
- Assign when
- The output configures a CI or CD system (pipelines, runners, Argo CD applications, Tekton).
- Not when
- The generator is merely built or tested in CI.
Cloud cloud
Manages resources of a public cloud provider.
- Assign when
- The output creates or configures resources of AWS, Azure, Google Cloud or a similar provider, including through their Kubernetes controllers.
- Not when
- The output only runs on a cloud-hosted cluster without touching provider resources.
Clusters clusters
Creates or bootstraps Kubernetes clusters.
- Assign when
- The output is the configuration a cluster tool reads to create or join nodes (talosctl machine configs, kind or k3d cluster configs, RKE2 or k3s config.yaml).
- Not when
- The generator configures workloads or add-ons inside an existing cluster, or provisions the underlying machines only.
Database database
Databases, caches and message brokers.
- Assign when
- The main purpose is to run or configure a data store or broker (PostgreSQL, Redis, RabbitMQ, Kafka).
- Not when
- The generator only passes a connection string to an application.
Helm helm
Renders a Helm chart or builds on one.
- Assign when
- The manifest declares a chart under
chartsor runshelm template. - Not when
- The output merely resembles a chart’s resources without using the chart, or the generator only writes a values file for someone else to install.
- Evidence
- a chart in the manifest or
helm templateinbinaries
No generator tagged helm yet.
Kubernetes kubernetes
Renders Kubernetes resources.
- Assign when
- The compiled output contains Kubernetes manifests (documents with apiVersion and kind).
- Not when
- The generator only renders files that end up in a Kubernetes cluster indirectly, such as a Dockerfile or Terraform for a managed cluster.
- Evidence
- Kubernetes manifests in the compiled output
Networking networking
Traffic between and into workloads.
- Assign when
- The main purpose is ingress, gateways, service mesh, DNS, network policy or CNI configuration.
- Not when
- The generator creates a Service or an Ingress as part of a larger application.
Observability observability
Metrics, logs, traces, dashboards or alerting.
- Assign when
- The main purpose is to collect, store, visualise or alert on telemetry (Prometheus, Grafana, Loki, OpenTelemetry).
- Not when
- The generator adds a ServiceMonitor or annotations to an otherwise unrelated workload.
Operators operators
Configures software that runs as a Kubernetes operator, through its custom resources.
- Assign when
- The main output are custom resources of an operator (ExternalSecret, ScaledObject, Certificate, ServiceMonitor) or the operator’s own installation.
- Not when
- The output contains CustomResourceDefinitions only as a side effect, or only plain built-in resources.
Security security
Secrets, identity, policy, certificates or scanning.
- Assign when
- The main purpose is a security function, such as secret delivery, certificates, admission policy or workload identity.
- Not when
- The generator only follows good security practice in its own output, such as non-root containers.
Terraform terraform
Renders Terraform configuration.
- Assign when
- The compiled output contains Terraform JSON (
*.tf.json). - Not when
- The generator renders Kubernetes resources that a Terraform provider later applies.
- Evidence
- Terraform JSON in the compiled output