RepoJournal
HashiCorp

@hashicorp

Terraform, Vault, Consul — infra-as-code for ops teams

Pick a date

  1. Sun 3 may
  2. Tue 5 may
  3. Wed 6 may
  4. Thu 7 may
  5. Fri 8 may
  6. Sat 9 may
  7. Sun 10 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

CONSUL-K8S PATCHES HELM VALUE PARSING BUG BLOCKING CUSTOM GATEWAY DEPLOYMENTS

By RepoJournal · Filed · About HashiCorp

A critical boolean-to-string conversion flaw in the consul-k8s CLI is preventing users from deploying custom gateways with resource limits, fixed today across two merged PRs.

The consul-k8s CLI was parsing Helm values.yaml files with strict type checking, rejecting legitimate boolean representations that the charts themselves accept [1]. This broke deployments where operators passed custom CPU/memory limits to custom gateway configurations because the resources-ocp filename wasn't being resolved correctly [2]. Both fixes shipped: the value parsing issue is resolved [3] and the custom gateway filename mismatch is patched [4]. In parallel, consul proper is hardening its container image with curl 8.20.0 to address seven CVEs [5], and UBI images are being bumped to 9.8 for additional security coverage [6]. Meanwhile, consul-ecs is migrating to v2 APIs and Go 1.26 [7], a significant modernization that requires testing against your ECS deployment patterns.

Action items

References

  1. [1] Fix boolean and string conversion issue (#5327) hashicorp/consul-k8s
  2. [2] fix(custom-gw): filename mismatch ↗ hashicorp/consul-k8s
  3. [3] Fix boolean and string conversion issue ↗ hashicorp/consul-k8s
  4. [4] fix(custom-gw): filename mismatch (#5334) hashicorp/consul-k8s
  5. [5] Fix CVEs ↗ hashicorp/consul
  6. [6] Ubi image version update-9.8 ↗ hashicorp/consul
  7. [7] Update imports to use v2 API and bump Go version to 1.26 ↗ hashicorp/consul-ecs
  8. [8] passing log-level chart to consul agent ↗ hashicorp/consul-k8s

FAQ

What changed in HashiCorp on May 21, 2026?
A critical boolean-to-string conversion flaw in the consul-k8s CLI is preventing users from deploying custom gateways with resource limits, fixed today across two merged PRs.
What should HashiCorp teams do about it?
Upgrade consul-k8s CLI immediately if using custom gateways with resource limits • Patch Consul containers with curl 8.20.0 to close CVE chain • Test consul-ecs v2 API migration against your ECS task definitions
Which HashiCorp repositories shipped on May 21, 2026?
hashicorp/consul-k8s, hashicorp/consul, hashicorp/consul-ecs

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.