Files
cozystack/packages/system/ouroboros/values.yaml
T
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

56 lines
3.1 KiB
YAML

ouroboros:
image:
repository: ghcr.io/lexfrei/ouroboros
# Pulled directly from the upstream lexfrei/ouroboros registry; this
# package is intentionally not mirrored under ghcr.io/cozystack/*.
# Air-gapped operators must mirror both this image and the OCI chart
# at oci://ghcr.io/lexfrei/charts/ouroboros separately. Bump the tag
# here together with OUROBOROS_CHART_VERSION in the Makefile.
tag: 0.8.1@sha256:cf285fe6f1eff6ac34e45871d4eef9c2f3ef590d76a6fc272019a9387519891d
controller:
# Host scenario default: mutate the live kube-system/coredns Corefile
# directly. The host CoreDNS on cozystack is Talos-managed and its
# Corefile does not include an `import /etc/coredns/custom/*.override`
# directive, so the alternative coredns-import mode (which writes into
# a separate ConfigMap that nothing reads) silently no-ops on the
# host. Tenant deployments override this back to coredns-import via
# the cozystack.defaultOuroborosValues helper in apps/kubernetes —
# tenants do run cozystack-coredns, which DOES include the import
# directive, so the import-CM mode works there.
mode: coredns
# gatewayApi watching is left at the upstream default (false). The
# host bundle template emits cozystack.ouroboros without injecting
# any controller.gatewayApi override because cozystack does NOT
# install Gateway-API CRDs cluster-wide on the host (system/
# gateway-api-crds is only registered in the kubernetes-application
# PackageSource — tenant scope). Forcing --gateway-api on a host
# without the CRDs would CrashLoopBackOff the controller on
# WaitForCacheSync against missing GVRs. The apps/kubernetes
# wrapper mirrors the per-tenant addons.gatewayAPI.enabled into
# this field for tenants that DO install Gateway-API.
proxy:
target:
# Tenant-cluster fallback default. A managed Kubernetes tenant
# cluster deploys ingress-nginx into cozy-ingress-nginx (its
# HelmRelease sets fullnameOverride: ingress-nginx +
# targetNamespace: cozy-ingress-nginx), so overriding the
# chart-default `ingress-nginx` namespace to cozy-ingress-nginx
# matches there; the chart-default serviceName lines up as-is.
#
# The HOST is different: extra/ingress deploys ingress-nginx into
# the root tenant namespace (publishing.ingressName, default
# tenant-root) as <short>-ingress-controller (e.g.
# root-ingress-controller), NOT cozy-ingress-nginx. The host
# platform bundle (core/platform templates/bundles/system.yaml)
# therefore overrides proxy.target.{namespace,serviceName} when it
# emits cozystack.ouroboros, derived from publishing.ingressName.
# This default is never effective on the host once that override
# lands.
#
# Leaving `host:` empty (chart-default) tells the proxy to compose
# the backend host at runtime as
# `<serviceName>.<namespace>.svc.<auto-detected-cluster-domain>`,
# which works on cozy.local (cozystack), cluster.local (kubeadm),
# or any other domain without operator override.
namespace: cozy-ingress-nginx