Infrastructure Patterns
When to Use What
| Tool |
Use For |
| Raw K8s YAML |
Simple deployments, one-off resources |
| Kustomize |
Environment variations, overlays without templating |
| Helm |
Complex apps, third-party charts, heavy templating |
| Terraform |
Cloud resources, infrastructure lifecycle |
| GitHub Actions |
CI/CD, automated testing, releases |
| Makefile |
Build automation, self-documenting targets |
| Dockerfile |
Container builds, multi-stage, multi-arch |
Quick Decisions
Kustomize when: Simple env differences, readable manifests, patching YAML
Helm when: Complex templating, third-party charts, release management
K8s Security Defaults
Every workload: non-root user, read-only filesystem, no privilege escalation, dropped capabilities, network policies.
GitHub Actions Patterns
- CI workflow: Lint, test, compile on PRs (run on both x86 + ARM)
- Release workflow: Multi-arch Docker build on tags (native ARM runners)
- Pin actions by SHA, least-privilege permissions
References
- KUBERNETES.md - K8s resource patterns
- TERRAFORM.md - Terraform module patterns
- GITHUB-ACTIONS.md - CI/CD workflow patterns
- MAKEFILE.md - Build automation patterns
- DOCKERFILE.md - Container build patterns
- templates/ - Ready-to-use templates
Commands
kubectl apply -k ./ # Apply kustomize
helm upgrade --install NAME . # Install/upgrade chart
terraform plan && terraform apply
Gotchas
- Terraform state lock contention: default 10-min lock timeout; bumped timeout doesn't help if the lock holder hung — force-unlock only after confirming the process is dead.
- Helm release name reuse on uninstalled-but-not-purged release fails install with "already exists" — use
--no-hooks + explicit purge, or never reuse names.
- Kustomize patches that match nothing silently produce empty diffs — verify with
kustomize build after every patch addition.
- Terraform
for_each over a computed value forces apply-time count — can cause spurious re-creation of resources between plans.
helm upgrade --install on a changed values schema can silently drop fields that no longer match — diff the rendered output, not just the values file.kubectl apply --server-side vs client-side conflicts when both have been used: client-side last-applied-config can shadow server-side managed fields without error.
1---2name: managing-infra3description: Infrastructure patterns for Kubernetes, Terraform, Helm, Kustomize, and GitHub Actions. Use when making K8s architectural decisions, choosing between Helm vs Kustomize, structuring Terraform modules, writing CI/CD workflows, or applying security best practices.4---5
6# Infrastructure Patterns
7
8## When to Use What
9
10| Tool | Use For |
11| ------------------ | --------------------------------------------------- |
12| **Raw K8s YAML** | Simple deployments, one-off resources |
13| **Kustomize** | Environment variations, overlays without templating |
14| **Helm** | Complex apps, third-party charts, heavy templating |
15| **Terraform** | Cloud resources, infrastructure lifecycle |
16| **GitHub Actions** | CI/CD, automated testing, releases |
17| **Makefile** | Build automation, self-documenting targets |
18| **Dockerfile** | Container builds, multi-stage, multi-arch |
19
20## Quick Decisions
21
22**Kustomize** when: Simple env differences, readable manifests, patching YAML
23**Helm** when: Complex templating, third-party charts, release management
24
25## K8s Security Defaults
26
27Every workload: non-root user, read-only filesystem, no privilege escalation, dropped capabilities, network policies.
28
29## GitHub Actions Patterns
30
31- **CI workflow**: Lint, test, compile on PRs (run on both x86 + ARM)
32- **Release workflow**: Multi-arch Docker build on tags (native ARM runners)
33- Pin actions by SHA, least-privilege permissions
34
35## References
36
37- [KUBERNETES.md](KUBERNETES.md) - K8s resource patterns
38- [TERRAFORM.md](TERRAFORM.md) - Terraform module patterns
39- [GITHUB-ACTIONS.md](GITHUB-ACTIONS.md) - CI/CD workflow patterns
40- [MAKEFILE.md](MAKEFILE.md) - Build automation patterns
41- [DOCKERFILE.md](DOCKERFILE.md) - Container build patterns
42- [templates/](templates/) - Ready-to-use templates
43
44## Commands
45
46```bash
47kubectl apply -k ./ # Apply kustomize
48helm upgrade --install NAME . # Install/upgrade chart
49terraform plan && terraform apply
50```
51
52---
53
54## Gotchas
55
56- **Terraform state lock contention**: default 10-min lock timeout; bumped timeout doesn't help if the lock holder hung — force-unlock only after confirming the process is dead.
57- **Helm release name reuse on uninstalled-but-not-purged release** fails install with "already exists" — use `--no-hooks` + explicit purge, or never reuse names.
58- **Kustomize patches that match nothing silently produce empty diffs** — verify with `kustomize build` after every patch addition.
59- **Terraform `for_each` over a computed value forces apply-time count** — can cause spurious re-creation of resources between plans.
60- **`helm upgrade --install` on a changed values schema** can silently drop fields that no longer match — diff the rendered output, not just the values file.
61- **`kubectl apply --server-side` vs client-side conflicts** when both have been used: client-side last-applied-config can shadow server-side managed fields without error.
julianobarbosa