Koios Automation Platform 2026.11.2 — release notes
Fix release of 2026.11.1 for platforms on an external PostgreSQL, published 2026-11-01 in the
private registry ghcr.io/koiosplatform. Catalog:
ghcr.io/koiosplatform/koios-operator-catalog@sha256:de01dda09d090b2709aa470d6d1a250bd2153bec2258518cb3c8b1749bbb8d54
(see olm-install.md).
Only the gateway operator changes. Every other image is the same as in 2026.11.1, with the same digest.
Upgrading from 2026.11.0 or 2026.11.1
Point the koios-operators CatalogSource at the new catalog digest. OLM upgrades the operators in
the stable-2026.11 and stable-2026.11-cluster-scoped channels (koios-operator.v2026.11.2
replaces v2026.11.1). Platforms with the managed PostgreSQL need no changes.
Platforms on an external PostgreSQL: rename the component database Secret fields before upgrading. They now use the same fields as the AnsibleAutomationPlatform resource. The previous names are rejected with a message that gives the new ones.
Before |
Now |
|---|---|
|
|
|
|
|
|
spec.database.database_secret (gateway) and spec.eda.event_stream.database_secret are
unchanged. Backups taken with 2026.11.0 or 2026.11.1 restore without changes: the previous names
are translated.
Fixes
An external database can be selected with
spec.database.database_secretalone. In 2026.11.0 and 2026.11.1 the API defaulteddatabase.managedtotrueand the platform was rejected unlessdatabase.managed: falsewas set explicitly.An invalid database Secret (missing, without a required key, or with a
typeother thanunmanaged) is reported by name with its cause, instead of “One or more items failed”.Restoring into an external PostgreSQL whose automation hub database has the
hstoreextension created by the administrator no longer fails with “must be owner of extension hstore”.A restore keeps the database mode of the backed up platform. The error for an external destination now explains how to choose a managed one (
spec_overrides.database.managed: true).
Validated
On Kubernetes (k3d), with gateway, controller, EDA and hub on an external PostgreSQL 15:
deployment, idle mode and deletion (the database and the Secrets are left untouched);
jobs, resource synchronization and rulebook activations;
backup, and restore from external to managed and from managed to external.
On OpenShift: upgrade through the channel from 2026.11.1.