riotpiaole
918ba9393f
Local charts: kafka-cluster (Strimzi Kafka+KafkaNodePool CRs, 3-replica KRaft
topology, 5Gi memory cap, Longhorn storage, pod anti-affinity), queue-crd
(Queue CRD + queue-operator Deployment/RBAC), management-service
(Deployment/Service/ConfigMap/HPA/Ingress, REST exposed externally via
cert-manager-issued TLS, raw gRPC kept cluster-internal per design.md §7a).
helmfile.yaml.gotmpl + releases.d/*.gotmpl wire strimzi-operator ->
kafka-cluster -> redis -> {queue-crd, management-service} via `needs:`.
Directory is releases.d, not helmfile.d as originally sketched in design.md
section 7b: Helmfile v1 treats a literal "helmfile.d" directory as a special
auto-discovery mode that conflicts with an explicit top-level helmfile.yaml.
Files use .gotmpl (required by Helmfile v1 for {{ }}-templated files) and
each declares its own environments: block, since nested helmfiles don't
inherit the parent's resolved values in this version.
Namespace is sqs throughout. environments/homelab.yaml carries no secrets.
Validated locally via helm lint/helm template (all 3 charts) and
`helmfile -e homelab build` (dependency ordering + value substitution) — no
cluster contact made. Live apply is a separate, explicitly-confirmed step.
29 lines
672 B
Go Template
29 lines
672 B
Go Template
environments:
|
|
homelab:
|
|
values:
|
|
- ../environments/homelab.yaml
|
|
---
|
|
repositories:
|
|
- name: bitnami
|
|
url: https://charts.bitnami.com/bitnami
|
|
|
|
releases:
|
|
- name: kmsvc-redis
|
|
namespace: {{ .Values.namespace }}
|
|
chart: bitnami/redis
|
|
version: 20.6.0
|
|
values:
|
|
- architecture: standalone
|
|
auth:
|
|
enabled: false
|
|
master:
|
|
persistence:
|
|
enabled: true
|
|
storageClass: {{ .Values.redis.storageClass }}
|
|
size: 2Gi
|
|
resources:
|
|
limits:
|
|
memory: {{ .Values.redis.memoryLimit }}
|
|
requests:
|
|
memory: {{ .Values.redis.memoryLimit }}
|