1 Commits

Author SHA1 Message Date
Bas Cancrinus
c9ecf577c4
fix(helm): drop rollingUpdate when a Deployment strategy is Recreate (#8336)
* fix(helm): drop rollingUpdate when a Deployment strategy is Recreate

The gateway and provisioner default to RollingUpdate with a rollingUpdate
block. Setting only `strategy.type: Recreate` renders both, which the API
server rejects ("may not be specified when strategy type is 'Recreate'").
A direct install can null the block, but a parent chart that depends on
this chart can't: Helm keeps the subchart's default. A single gateway on a
ReadWriteOnce home PVC needs Recreate, since the new Pod can't attach the
volume on another node while the old one holds it.

A `deer-flow.strategy` helper renders the strategy and drops rollingUpdate
for Recreate; both Deployments use it. Defaults render unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(helm): note the Helm 4 server-side apply case when switching to Recreate

A release whose manifest omitted strategy leaves the API-server-defaulted
rollingUpdate unowned; server-side apply then can't remove it and the
switch to Recreate is rejected. Document running that upgrade with
--server-side=false.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 08:10:45 +08:00