[fatih-acar]

Why

• Problem: feat!: remove the NATS message bus and cache drivers infrahub#11210 removes the NATS JetStream driver for the message bus and the cache. Once Infrahub ships it, a configuration that sets INFRAHUB_BROKER_DRIVER or INFRAHUB_CACHE_DRIVER to nats fails to load. The infrahub chart still offers a nats subchart, version 1.1.12, that nats.enabled turns on. (Chart.yaml on stable, values.yaml on stable)
• Change: this pull request removes the subchart, its values and every NATS mention.
• Order: merge this pull request after feat!: remove the NATS message bus and cache drivers infrahub#11210, and before the Infrahub release that contains it. Every final Infrahub release publishes the infrahub chart from stable, so merging this pull request earlier would remove the subchart for an Infrahub version that still accepts nats.

What changed

• charts/infrahub/Chart.yaml: the nats dependency is removed.
• charts/infrahub/values.yaml: the nats block (enabled: false, config.jetstream.enabled: true) is removed.
• charts/infrahub/README.md: the dependency row and the two nats.* value rows are removed by hand. helm-docs produces the same rows; it would also change the prefectTag row from 1.11.4 to 1.11.9, which was out of date before this change and is left as is.
• tests/e2e/test_tracing_optout.py: nats.enabled: false is removed from the values that trim the stack.
• AGENTS.md: the infrahub chart description no longer lists NATS.
• Changelog fragments, type removed, in charts/infrahub/changelog/ and charts/infrahub-enterprise/changelog/. The infrahub-enterprise chart gets this change when its infrahub pin moves to a release of the infrahub chart that contains it.

No template read the nats values. Enabling nats only deployed a NATS server, which Infrahub used when the operator also set INFRAHUB_BROKER_DRIVER or INFRAHUB_CACHE_DRIVER to nats.

How to test

make lint
helm dependency update charts/infrahub
helm template infrahub charts/infrahub
helm template infrahub charts/infrahub --set nats.enabled=true
uv run pytest -v -m infrahub tests/e2e

Results:

• make lint passes for every chart.
• With default values, helm template renders the same manifests as stable, apart from the RabbitMQ Erlang cookie, which the subchart generates at random on each render.
• With nats.enabled=true, stable renders 48 objects and this branch renders 40, the same as with default values. Helm accepts the leftover nats value without an error.
• The end-to-end tests were not run locally. CI runs them for a change to charts/infrahub/ and tests/.

Impact and rollout

• A release whose values set nats.enabled: true (infrahub.nats.enabled: true with infrahub-enterprise) loses the NATS server when the chart is upgraded. If that release set INFRAHUB_BROKER_DRIVER or INFRAHUB_CACHE_DRIVER to nats, it must switch to RabbitMQ and Redis first. The changelog fragments say so.
• What happens to a NATS volume claim on upgrade was not checked.
• With default values nothing changes.

🤖 Generated with Claude Code