docs(specs): switch deploy approach from Helm to Kustomize#60
Merged
Conversation
Replaces the architecture spec's "Helm conventions" reference with Kustomize base + per-environment overlays at deploy/kustomize/. Rationale in the new paragraph: chart-template indirection is overkill for our scope; plain-YAML overlays match the project's preference for explicit composition over template substitution. Implementation follows in a separate plan + PR (drops deploy/charts/ + flips GHA workflows to `kubectl apply -k`). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
deploy/kustomize/.Spec-only
Implementation (kustomize manifests + Helm-chart retirement + GHA flip) lands in the follow-on PR against
feat/sandbox-deploy. This one is just the architecture spec amendment so specs lead code per the project's spec-driven workflow.Test plan
specs/architecture.mdmatches the impl that's about to merge🤖 Generated with Claude Code