Skip to content

feat(eks): remove dead eks_blueprints_addons; drop helm + kubectl providers (v5.0.0) - #53

Merged
obezpalko merged 1 commit into
mainfrom
feat/v5-chunk-b-drop-blueprints-addons
Jul 31, 2026
Merged

obezpalko merged 1 commit into
mainfrom
feat/v5-chunk-b-drop-blueprints-addons

Conversation

@obezpalko

@obezpalko obezpalko commented Jul 31, 2026 •

Copy link
Copy Markdown

User description

Chunk B of the k8s-free module (v5.0.0). Removes module.eks_blueprints_addons — it deploys nothing (only aws_cloudwatch_metrics, which defaults false and no wrapper enables) — and drops the helm + third-party gavinbunney/kubectl providers (both required_providers and the provider config blocks in providers.tf).

Confirmed the upstream terraform-aws-modules/eks v21 needs only aws/tls/time, so nothing else pulls helm/kubectl. terraform init+validate pass; terraform providers now lists only kubernetes (from the remaining kubernetes_* resources, removed in later chunks).

Versioned/no cluster impact until a wrapper bumps ?ref. Container Insights, if ever needed, goes on the comet-infra umbrella instead.

🤖 Generated with Claude Code


Generated description

Below is a concise technical summary of the changes proposed in this PR:
Remove the dead eks_blueprints_addons path from the EKS stack and trim the comet_eks module inputs so the cluster is managed only through the remaining native EKS and Kubernetes resources. Drop the unused helm and kubectl provider setup from the root configuration and module constraints, leaving only the providers still needed by the surviving Kubernetes flow.

TopicDetails
EKS addons cleanup Remove the dead eks_blueprints_addons module and the eks_aws_cloudwatch_metrics input from the comet_eks EKS composition.
Modified files (4)
  • main.tf
  • modules/comet_eks/main.tf
  • modules/comet_eks/variables.tf
  • variables.tf
Latest Contributors(2)
UserCommitDate
alexb@comet.comfeat(eks): remove dead...July 31, 2026
CRThazeMerge pull request #52...July 29, 2026
Provider cleanup Drop the unused helm and kubectl provider declarations and version constraints from the root and EKS module setup.
Modified files (3)
  • modules/comet_eks/versions.tf
  • providers.tf
  • versions.tf
Latest Contributors(2)
UserCommitDate
alexb@comet.comfeat(eks): remove dead...July 31, 2026
jms200upgrade upstream eks/a...June 12, 2026
Review this PR on Baz | Customize your next review

…viders (v5.0.0)

module.eks_blueprints_addons deployed nothing — its only remaining feature
(aws_cloudwatch_metrics) defaults false and no wrapper enables it. Delete the
module block + the eks_aws_cloudwatch_metrics var (module + root + pass-through)
+ the now-unused local.auto_mode_controller_config, and remove the helm and
gavinbunney/kubectl providers (required_providers in both versions.tf AND the
provider "helm"/"kubectl" config blocks in providers.tf).

Verified: the upstream terraform-aws-modules/eks (v21) needs only aws/tls/time,
so nothing else pulls helm/kubectl. `terraform init`+`validate` pass; the module
now requires only aws/tls/time/kubernetes/random. If Container Insights is ever
needed, add aws-cloudwatch-metrics to the comet-infra umbrella instead.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment thread variables.tf
default = false
}

variable "eks_external_dns" {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale tfvars breaks planning

The eks_aws_cloudwatch_metrics input was removed from the root module, but terraform.tfvars still sets eks_aws_cloudwatch_metrics = false, so terraform plan/apply will fail on the undeclared entry — should we delete the matching line at the same time, or keep the input until all callers are updated?

Severity

Want Baz to fix this for you? Activate Fixer

@obezpalko
obezpalko merged commit 61dea00 into main Jul 31, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant