Andrei Kvapil d62056ef03 fix(foundationdb)!: pick the version from a fixed list ...

cluster.version took any string and passed it to the operator as the
FoundationDB version, so a tenant chose the image tag rather than a
supported release line. The application now takes version (v7.4, v7.3,
v7.1) and maps it to a tag through files/versions.yaml, the same way
postgres and mariadb do.

The lines are the ones the pinned operator ships client libraries for,
which hack/update-versions.sh reads from the operator chart. The map
keeps v7.3 on 7.3.63, the previous default, so a cluster that never set
the version renders exactly as before.

Assisted-by: LLM
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>

2026-10-23 19:14:15 +05:00

..

chainsaw-test.yaml

fix(tests): let HR-Ready asserts outlive the install they wait on

2026-10-01 17:40:21 +03:00

foundationdb.yaml

fix(foundationdb)!: pick the version from a fixed list

2026-10-23 19:14:15 +05:00