Files
cozystack/packages/system
IvanHunters 75eebb5f3c feat(kube-ovn): bump kube-ovn to v1.15.26
Update kube-ovn from v1.15.10 to v1.15.26.

v1.15.26 removes the checkDBClusterIntegrity check from the OVN leader
checker (pkg/ovn_leader_checker/ovn.go). In v1.15.10 that check called
os.Remove on a healthy local raft DB whenever a leader observed fewer
members than expected (ovn.go:367). That count drops below the target
transiently during cluster growth, a rolling restart, or recovery after
a node address change, so the check could delete a valid DB and leave
ovn-central unable to elect a leader. The function is gone in v1.15.26,
so the DB is no longer deleted.

The chart is re-vendored with `make update`, which re-pulls
charts/kube-ovn from the v1.15.26 tag, re-applies patches/mtu.diff, and
regenerates the image build args. This brings the full v1.15.26 chart:
the reworked master-node affinity helpers, the widened kube-ovn CRD
schema (bandwidth ingress/egress become int-or-string, u2oFeatures
added), and the new OVN_CENTRAL_MODE (cluster/single) support with its
central-svc, central-pvc and central-hcp-rbac templates. OVN_CENTRAL_MODE
defaults to cluster (raft on hostPath), so an in-place upgrade keeps the
existing topology.

Two vendored patches are dropped as now upstream in v1.15.26:
fix-keepvmip-portgroup.diff (hasAliveSiblingVMPod, pod.go:2437) and
fix-vmim-scheduling-retry.diff (scheduling requeue, kubevirt.go:195).
fix-vmim-target-pod-retry.diff is kept: v1.15.26 still returns nil at
kubevirt.go:215.

The image ref stays digest-pinned (repository + tag@sha256), which the
promote-retag release contract requires for a cozystack-built image. The
digest is carried over from v1.15.10 as a placeholder and is refreshed to
the real v1.15.26 image by the release-candidate digest-vendoring step;
no PR or main job rebuilds it.

Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
2026-09-22 13:08:39 +03:00
..
2026-03-25 15:57:25 +05:00
…