mr0xb/dotfiles
Watch
1
0
Fork
You've already forked dotfiles
 0
mirror of https://github.com/mr0xb/dotfiles.git synced 2026-08-28 20:04:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

updates

Browse source
This commit is contained in:
mr0xb 2026-05-22 15:54:54 -04:00
commit a89c144cd9
No known key found for this signature in database
GPG key ID: D61C4E28AAE1BC5C
476 changed files with 89929 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.claude/projects/-Users-steve-briggs-projects-IAC/memory/MEMORY.md Normal file
View file

@ -0,0 +1 @@
- [Platform-tier components use Terraform, not Flux](feedback_platform_components_use_terraform.md) — for `eks-cluster-applications` plumbing, default to TF/helm provider; Flux is for apps

11
.claude/projects/-Users-steve-briggs-projects-IAC/memory/feedback_platform_components_use_terraform.md Normal file
View file

@ -0,0 +1,11 @@
---
name: Platform-tier components in IAC use Terraform, not Flux
description: When deploying telemetry/observability/platform infra in this repo, prefer Terraform/helm-provider over Flux even when Flux is available
type: feedback
originSessionId: 9c7db84f-6d53-4918-8d06-638ada15b7e9
---
For platform-tier components in the IAC repo (telemetry, observability, anything that lives alongside otel-collector / cilium / external-secrets / fluxcd in `terraform/iac-library/aws/compute/eks-cluster-applications/`), prefer **Terraform with the helm provider** over deploying via Flux — even when the user's first instinct mentions Flux.
**Why:** Sir Charles asked "what are the benefits of deploying X via Flux vs Terraform" while planning the Vector redaction layer (2026-05-05). I had initially proposed Flux because the user said "using flux" in their original ask. He pushed back, noted that OTel itself is Terraform-managed and Vector is plumbing rather than an application, and chose Terraform after I laid out the tradeoffs honestly. Co-locating telemetry components keeps the wire diagram in one place and lets atomic terraform applies coordinate cross-component changes (e.g. version-bumping the OTel module's exporter target alongside the new Vector deployment).
**How to apply:** When designing new platform-tier components for clusters managed by `eks-cluster-applications`, propose Terraform/helm-provider as the default. Flux is the right answer for *applications* (license-manager, crow, saas-tenant-manager, etc. — things in `application-deployment*/flux/`), not for plumbing. If the user explicitly says "use Flux" for a platform component, surface the tradeoff before just doing it — they may not have considered the Terraform alternative.