Service Helm charts

Every service owns an independently installable, observability-neutral Helm chart.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

Behavior

Chart.yaml identifies the service chart.
values.generated.yaml contains replaceable generator defaults.
values.yaml contains project-specific overrides preserved across regeneration.
values.schema.json validates the chart contract.
Generated templates create workload, Service, ConfigMap, ServiceMonitor and optional extra objects.
kubernetesWorkloadType selects Deployment or StatefulSet from the service graph.

Helm chart structure

Files emitted for each generated service.

FileOwnershipDescription

helm/Chart.yamlChart metadata

Name, version and application identity.

helm/values.generated.yamlGenerated defaults

Image, ports, probes, resources and generated runtime values.

helm/values.yamlPreserved overrides

Project and environment-specific chart settings.

helm/values.schema.jsonGenerated schema

Validation for public chart values.

templates/workload.generated.yamlGenerated

Deployment or StatefulSet with probes and environment wiring.

templates/service.generated.yamlGenerated

Service ports derived from connectors and handlers.

templates/configmap.generated.yamlGenerated

Non-secret runtime configuration.

templates/servicemonitor.generated.yamlGenerated

Prometheus scrape contract where the runtime uses pull metrics.

templates/extra-objects.generated.yamlGenerated

Optional graph-dependent resources.

templates/_helpers.generated.tplGenerated

Canonical labels and names.

Production override template

# <service-name>/helm/values.yaml
image:
  repository: <registry>/<service-name>
  tag: <moduleVersion>
resources:
  requests:
    cpu: 250m
secretEnvFrom:
  - <service-name>-production