You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Split the single KividbCluster CRD into five (kividb.io/v1alpha1): KividbCluster (topology, storage, scheduling, Services, monitoring,
failover), KividbConfig (reusable kividb.conf directives + TLS
settings), KividbAclConfig (reusable ACL users / requirepass), KividbSnapshotConfig (reusable backup schedule/destination/retention),
and KividbSnapshot (operator-created record of one backup run). A
StackGres-style split: configuration/ACLs/backup destinations are now
independent, reusable objects referenced by name
(spec.configRef/spec.aclConfigRef/spec.snapshotConfigRef) instead
of embedded fields. spec.auth, spec.backup, and spec.kividbConfig
no longer exist on KividbCluster.
spec.image is now the sole field determining which kividb image runs.
Removed spec.version and the operator's automatic quay.io/kividbio/kividb:v<version>[-<variant>] tag construction — the
operator never derives or modifies an image reference itself anymore.
Leave spec.image unset for a floating, unpinned default tag; set it
explicitly to pin a version.
spec.variant (standard/tls/lua/full) is now purely
informational: it tells the operator whether to wire up variant-specific
pod configuration (TLS cert mounting/CLI flags), but no longer
influences image resolution. A likely spec.image/spec.variant
mismatch, or TLS enabled in a KividbConfig without a matching variant,
now surfaces as a guidance Event (VariantGuidance/ TLSVariantMismatch) via kubectl describe kividbcluster rather than
being silently wrong.
KividbCluster.status.backup removed — backup history now lives on KividbSnapshot objects (kubectl get kdbs -l kividb.io/cluster=<name>),
which carry per-run detail (source pod/role, object key, size, duration)
the old single status block couldn't.
Added
KividbSnapshotConfig.spec.source: master|replica to choose which
role's pod a scheduled backup is taken from (master is the default
and recommended choice).
values.schema.json for the Helm chart.
Guidance Events (see above) surfaced on KividbCluster reconcile.
Extensive rewrite of all docs for the new CRD architecture, plus docs/ROADMAP.md (0.2.0/1.0.0 planning and known upstream kividb
issues found via live testing) and docs/VERSIONING.md (how an
external site fetches these docs at a specific released version via
git refs).
Fixed
TLS settings (tls-port/tls-cert-file/tls-key-file/ tls-ca-cert-file) are now also passed to the kividb container as CLI
flags, not only written into the rendered kividb.conf — live testing
found kividb's --configfile parser currently ignores these directives
when file-sourced, even though the identical CLI flags are documented
and accepted.
Security
Bumped the builder image for all three published images
(kividb-operator, kividb-operator-agent, kividb-operator-gui) from golang:1.23-bookworm to golang:1.26-bookworm, and bumped golang.org/x/net (0.28.0→0.56.0), golang.org/x/oauth2
(0.21.0→0.27.0), golang.org/x/sys (0.24.0→0.46.0), and golang.org/x/text (0.17.0→0.39.0) — addressing a batch of stdlib and
dependency CVEs (including a critical crypto/tls session-resumption
issue, CVE-2025-68121) reported against the 0.1.0 images.