Skip to content

refactor(k8s): reorganize Helm templates into common/aws/onprem + per-component subfolders #5892

Description

@aicam

Task Summary

Reorganize the flat bin/k8s/templates/ directory into a clear, self-documenting layout, as the foundation for the AWS/EKS unification series (parent: #5891).

Two levels of grouping, both behavior-neutral (Helm renders templates/** recursively, so moving files into subdirectories does not change rendered output):

  1. By where they applytemplates/common/ (shared by every deployment), templates/onprem/ (minio-persistence.yaml), and templates/aws/ (placeholder for the AWS-only, value-gated templates added by later sub-tasks; empty for now).
  2. Within common/, by component — one subfolder per service holding all of its manifests (e.g. common/access-control-service/, common/gateway/, common/workflow-computing-unit-manager/, common/workflow-computing-unit-pool/).

Also adds templates/README.md documenting the convention, a .helmignore so *.md/.gitkeep are not loaded as manifests, and realigns values-development.yaml with values.yaml (image registry/tag + the AUTH_JWT_SECRET dev-default).

Verified no-op: helm template output is identical before/after (102 resources), helm lint passes, and the reorganized chart was smoke-tested end-to-end on minikube.

Addressed by #5757.

Task Type

  • Refactor / Cleanup
  • DevOps / Deployment / CI

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions