Koios Automation Platform 2026.11.7 — release notes

Published 2026-11-07 in the private registry ghcr.io/koiosplatform. Catalog: ghcr.io/koiosplatform/koios-operator-catalog@sha256:46622cd8bd9cc6db27d91b0a811bb32800c0ce1f74bd4638b47564eb97b38565 (see olm-install.md).

A licensing and notices release: no intended functional changes and no KoiosPlatform changes.

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 (the 2026.11.7 bundles replace the 2026.11.6 ones), and the platform rolls out the new images. Without OLM, apply kustomize/operators from the 2026.11.7 tag of koios-installer.

Changes

  • Modification notices. Each image that Koios builds from a modified upstream source now lists those modifications, with the files they touch, in /licenses/koios/NOTICE.modifications, and the installer NOTICE lists them for every image. Every upstream file that Koios patches also carries a dated Koios modification comment (controller install bundle, UI, EDA and Hub operator roles, pulpcore in the automation hub image).

  • Licenses. The automation hub (galaxy_ng) and the hub operator (galaxy-operator) are declared as GPL-2.0-or-later, as their sources state; the hub operator image was labelled Apache-2.0 and now also includes the upstream COPYRIGHT file.

Images

The controller, UI and automation hub images are rebuilt: the source changes are the notice comments, and the About dialog shows 2026.11.7. The gateway, EDA and execution environment images are the 2026.11.6 ones with a new licenses layer; their binaries are unchanged. The four operators are rebuilt to carry the new image digests and patch notices. The decision environment, Valkey, Envoy and PostgreSQL are the 2026.11.6 images.

Validated

  • OpenShift (single-node, 4.21): upgrade from 2026.11.6 through the stable-2026.11-cluster-scoped OLM channel, operator Succeeded, platform Successful on the new images, and a job through the gateway.

  • Kubernetes (k3d): the same checks with the manifests of the installer; the node install bundle keeps the receptor group fix.