RepoJournal
HashiCorp

@hashicorp

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

Pick a date

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

The Wire · Showcase

BOUNDARY WORKER HELM OVERHAULS TEST MATRIX, NOMAD AUTOSCALER SHIPS JSONENCODE SUPPORT

By RepoJournal · Filed · About HashiCorp

Boundary's Kubernetes validation just got real - switching from KIND binaries to actual versioned nodes means the chart now proves it works on the K8s versions you're actually running.

The big structural win comes from boundary-worker-helm [1], which ditched a validation theater approach that downloaded KIND binaries without actually testing against different Kubernetes API server versions. Now each CI run targets a specific kindest/node image pinned to real K8s releases and runs them in parallel, so you know the chart ships tested on 1.26, 1.27, and beyond. On the policy authoring side, nomad-autoscaler landed jsonencode support [2] for file-based policies, which means users writing APM queries can stop hand-escaping JSON strings and write readable HCL objects instead. The Instana plugin integration just got less painful. All three Nomad ecosystem projects pushed nightly snapshots [3][4][5], so if you're running bleeding edge, pull and test before the next stable cut. Compliance automation also caught up with boundary-worker-helm PR template updates [6][7] - standard HCP boundary compliance stuff, review and merge to stay in good standing.

Action items

References

  1. [1] Convert acceptance matrix from KIND-binary to Kubernetes-version, parallelize in CI ↗ hashicorp/boundary-worker-helm
  2. [2] enable jsonencode in file policy decoding ↗ hashicorp/nomad-autoscaler
  3. [3] nightly ↗ hashicorp/nomad-autoscaler
  4. [4] nightly ↗ hashicorp/nomad-driver-podman
  5. [5] nightly ↗ hashicorp/nomad-pack
  6. [6] [Compliance] - PR Template Changes Required ↗ hashicorp/boundary-worker-helm
  7. [7] [Compliance] - PR Template Changes Required (#55) hashicorp/boundary-worker-helm

FAQ

What changed in HashiCorp on June 27, 2026?
Boundary's Kubernetes validation just got real - switching from KIND binaries to actual versioned nodes means the chart now proves it works on the K8s versions you're actually running.
What should HashiCorp teams do about it?
Review boundary-worker-helm PR#56 and merge - the test matrix fix validates against real Kubernetes versions • Test nomad-autoscaler with jsonencode policies if you're using Instana or similar APM integrations • Pull latest nightly builds from nomad-autoscaler, nomad-driver-podman, and nomad-pack to catch regressions early
Which HashiCorp repositories shipped on June 27, 2026?
hashicorp/boundary-worker-helm, hashicorp/nomad-autoscaler, hashicorp/nomad-driver-podman, hashicorp/nomad-pack

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.