Files
Aleksei Sviridkin d542f66368 fix(ouroboros): render controller rollout strategy in every mode
Bump the chart and controller image to 0.8.1, which renders the
controller Deployment's rollout strategy in every controller.mode
instead of only in external-dns mode.

Up to 0.8.0 the chart rendered a strategy only in external-dns mode, as
type: Recreate, and nothing in the other modes. The apiserver defaults a
rollingUpdate block onto a Deployment created without one, so switching
a live release into external-dns laid Recreate on top of that defaulted
block and the apiserver rejected the object:

  spec.strategy.rollingUpdate: Forbidden: may not be specified when
  strategy `type` is 'Recreate'

The strategy is now identical across all modes, so no mode switch
changes a strategy field at all.

This is a latent break rather than an active one: the host pins coredns
and tenants pin coredns-import, neither of which rendered a strategy in
0.8.0, and no shipped configuration selects external-dns. But
controller.mode is user-settable and the chart supports the mode, so the
transition is reachable by configuration.

It surfaces only under server-side apply, which helm-controller uses by
default, so no local helm upgrade reproduces it: a client-side strategic
merge carries retainKeys on strategy and clears rollingUpdate on the way
through. The rendered strategy is pinned on all three modes, external-dns
included — it is the only mode that ever rendered Recreate, so a bump
that re-gated the block would otherwise slip past a coredns-only suite.

0.8.1 also carries an upstream bump of the cleanup-hook kubectl image
to 1.36.1.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-07-16 16:18:37 +03:00
..