Koios Automation Platform 2026.11.3 — release notes
Published 2026-11-01 in the private registry ghcr.io/koiosplatform. Catalog:
ghcr.io/koiosplatform/koios-operator-catalog@sha256:1aa64ef15b04e14cd04d1cbe8ccaa6d191a0a580f2d002f9403bff124f9c8b3b (see olm-install.md).
The gateway, EDA and automation hub operators change. Every other image is the same as in 2026.11.2, with the same digest.
Upgrading from 2026.11.x
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.3
replaces v2026.11.2). No KoiosPlatform changes are needed.
New
Verified TLS to an external PostgreSQL. With sslmode: verify-ca or verify-full in the
database Secrets, every component verifies the server certificate: gateway, controller, EDA,
automation hub, and the pods that check the database and run backups and restores. A private CA
goes in bundle_cacert_secret (key bundle-ca.crt).
EDA now honors the
sslmodeof its database Secret. Before, it connected withallow: it tried an unencrypted connection first and never verified the server.EDA and automation hub install the CA before their database migrations; before,
verify-*with a private CA kept their pods inInit:CrashLoopBackOff.An unknown CA or a host name that is not in the certificate is reported before anything is deployed, with the fix (“Put the CA that signed the server certificate in bundle_cacert_secret”).
Pods that cannot be scheduled. When a component cannot be placed (not enough memory or CPU, node selectors, taints, volume node affinity), the platform status now gives the scheduler reason and the fields to adjust, instead of “unknown playbook failure”. This applies to the controller, gateway, Redis, PostgreSQL, EDA and automation hub.
Notes
requireandpreferbehave as before: the server certificate is verified only withverify-*.For EDA, a managed PostgreSQL without TLS now uses
prefer, which falls back to an unencrypted connection, so nothing changes in practice.