Release 2.0.0: OOP platform chart with Keycloak, shared PostgreSQL, NATS and Data Lab

Dimitrios Gogosrequested to merge
develop into main

Release v2.0.0 of the oop-platform umbrella chart, the reference deployment of OOP. Merges develop into main. Tag v2.0.0 after merge.

OEG, SRM, Federation Manager, AI2 and Portal move to their 2.0 releases. The platform gains Keycloak, one shared PostgreSQL, NATS with JetStream and an optional Data Lab. MongoDB is gone.

What's new since v1.0.0-release

Platform services

  • Keycloak (new): realms oop (portal users, app providers, OEG tokens) and federation (FM partners). Includes organization tenancy, a themed login page, an initial admin that must set a new password at first login, and CAMARA operation scopes (including QoD and Traffic Influence) on portal tokens.
  • Realm setup job (new): configures the realm, API products and a provisioner client for API-client management. It can be re-run after a realm is deleted.
  • PostgreSQL 18.6 (new, shared): one database and role per component (OEG, SRM, FM, Keycloak, Portal).
  • NATS (new): official NATS chart, with JetStream and a 2Gi file store for Federation Manager. Includes a smoke test.
  • Data Lab 0.1.0 (new, off by default): piveau hub and search, Virtuoso, Elasticsearch, Data Lab UI and API.

Component charts (all 2.0.0)

  • OEG: rewritten for OEG 2.0. Generated, persisted encryption keys.
  • SRM: rewritten for SRM 2.0 with tf-sdk control paths. Single bootstrap with validated credential mounts, capability-instance monitor interval, and a setting for when FM is disabled.
  • Federation Manager: rewritten for FM 2.0. The internal API is reachable through a ClusterIP-only Service, and it uses the shared Keycloak, NATS and PostgreSQL.
  • AI2: chart 2.0.0 with Redis for session memory. It points at the OEG 2.0 service root and no longer re-pulls the wait-for-mcp image on every start.
  • Portal: chart 2.0.0 with clearer descriptions and managed secrets.

Removed

  • MongoDB from OEG, SRM, FM and the kind setup.
  • The artefact-manager from SRM and the kind setup.
  • 1.x-only env vars, kompose annotations, the duckdns ingress, the FM 1.x config file and the cluster-admin token.

Tooling and docs

  • scripts/kind-bootstrap.sh and helm-deploy.sh updated (NATS repo added). The kind scripts print access URLs from the live Services.
  • READMEs rewritten for the 2.0 charts: components, architecture, Keycloak API-client roles, realm re-run and the SRM image requirements.
  • Test for the SRM bootstrap.
  • global.auth.enabled: a localhost-only switch that skips Keycloak and Federation Manager. The Federation Manager switch moved under federation-manager.
  • Apache License 2.0 added.

Upgrade notes

  • Not an in-place upgrade from 1.x: MongoDB data is not migrated. Redeploy on a fresh cluster.
  • Subchart values moved, so review custom values files, especially auth and FM switches.
  • Fill in the Keycloak, provisioner and Groq secrets as described in the README.
  • Data Lab is off by default. Enable it with datalab.enabled.
  • The SRM image must be built as documented in the SRM chart README.

Checks

  • helm lint --strict and default/kind helm template pass at 805a75a6 (local checks)
  • Fresh kind-bootstrap.sh + helm-deploy.sh brings all pods ready
  • Login through Keycloak works, and the realm setup job completes
  • OEG → SRM → FM events flow over NATS
  • All 8 bootstrap tests pass (tests/test_srm_bootstrap.py, local checks at 805a75a6)

Release steps

  1. Merge to main.
  2. Tag v2.0.0 on the merge commit.``
Edited by Konstantinos Togias

Merge request reports