CAIPE Blog

Release 0.5.8 — Skills FGA, catalog API keys BFF, and RBAC migrations

2026-06-05T00:00:00.000Z

Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.8 (when published) Previous release: 0.5.4

Highlights

0.5.8 continues enterprise RBAC work: skill team shares reconcile through the shared OpenFGA shareable-resource module, catalog API keys can be minted from the CAIPE UI BFF without the supervisor, and admin ReBAC migrations cover agent/skill FGA backfills. See the upgrade guide below for the catalog API key hash change before upgrading production.

What's New

Skills and catalog

Catalog API keys in the BFF — mint, list, and revoke keys via /api/catalog-api-keys without proxying to the supervisor (see breaking change if you already minted keys).
Skill FGA reconcile — per-skill team shares use the shared reconcileShareableResource path; admin migration agent_skill_openfga_reconcile_v1 backfills owner and team tuples from Mongo.

RBAC

Agent user:* wildcard — visibility changes correctly add/remove org-wide grants on dynamic agents.
Skills team sharing — members can team-share skills from the Skill Builder with the same teams picker pattern as agents and knowledge bases.

Breaking Changes

Catalog API key hash

Stored catalog API key digests changed algorithm:

	Before	After (0.5.8)
Algorithm	SHA-256 of `pepper + ":" + secret`	HMAC-SHA256 with `CAIPE_CATALOG_API_KEY_PEPPER` (or `SKILLS_API_KEY_PEPPER`) as the HMAC key
BFF	N/A or legacy proxy	`ui/src/lib/catalog-api-keys.ts`
Python	`skills_middleware/api_keys_store.py`	Same HMAC format as BFF

Impact: Any row in the catalog_api_keys collection created before this change will fail verification after upgrade. Clients must receive a newly minted key.

Not affected: Key format on the wire is unchanged ({key_id}.{secret}). Pepper env vars are unchanged; only how the secret is hashed at rest changed.

Security

Catalog key hashing uses HMAC-SHA256 and unbiased randomInt for secret generation (CodeQL-hardened).
Set CAIPE_CATALOG_API_KEY_PEPPER to a long random value in production (see ui/env.example).

Known Issues

None documented for this pre-release note.

Upgrade

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.8 \
  -f your-values.yaml

Upgrade Guide: 0.5.4 → 0.5.8

Overview

Most deployments can upgrade the chart first, then run admin ReBAC migrations from Admin → ReBAC migrations. If you use catalog API keys (Skills Gateway / X-Caipe-Catalog-Key), plan a short key rotation window — see Catalog API key hash below.

Catalog API key hash

Required when: the catalog_api_keys MongoDB collection contains keys minted before 0.5.8 (BFF or supervisor).

Skip when: the collection is empty or you do not use catalog API keys.

1. Confirm pepper is set consistently

Use the same pepper on the CAIPE UI (BFF) and any Python path that validates keys (supervisor / skills middleware):

# ui deployment / secret
CAIPE_CATALOG_API_KEY_PEPPER=<openssl rand -hex 32>

# skills middleware / supervisor (if applicable)
SKILLS_API_KEY_PEPPER=<same value>

Do not change the pepper during rotation unless you intend to invalidate all keys.

2. Rotate keys

For each active key:

In the UI (or via API), revoke the old key_id.
Mint a new key and distribute the new {key_id}.{secret} to clients (CI, local CAIPE_CATALOG_KEY, install scripts, etc.).
Update automation that cached the old secret.

Optional (dev/test only): drop the collection and re-mint from scratch:

// MongoDB — destructive; production use revoke + mint instead
db.catalog_api_keys.deleteMany({})

3. Verify

curl -sS -H "X-Caipe-Catalog-Key: " \
  "https:///api/skills/catalog" | head

Expect 200 (or your normal catalog response), not 401.

Helm Values Changes

Document full values.yaml diff when the 0.5.8 chart is published. Set catalog pepper via existing UI/skills env wiring (see ui/env.example).

Data Migrations

Run pending migrations from Admin → ReBAC migrations, including when applicable:

agent_skill_openfga_reconcile_v1 — backfill skill owner/team FGA tuples
agent_shared_team_grants_backfill_v1 — agent shared_with_teams → OpenFGA
Other 0.5.8 manifest entries shown as behind in the migrations UI

Upgrade Runbook

1. Rotate catalog API keys (if used)

Complete Catalog API key hash before or immediately after deploy so clients are not left with invalid keys.

2. Update chart version

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.8 \
  -f your-values.yaml

3. Run ReBAC migrations

Use the admin migrations UI with the confirmation strings shown per migration.

4. Verify

Skills list/catalog with a new catalog API key
Team-shared skills visible to team members after FGA reconcile migration
Dynamic agent global/team visibility behaves as expected

Release 0.5.2 — RAG Access Control and Gateway Routing

2026-05-29T00:00:00.000Z

Released: 2026-05-29 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.2 Previous release: 0.5.1

Highlights

0.5.2 completes the OpenFGA relationship-based access model for RAG and Knowledge Bases — knowledge bases can now be shared with teams, every Knowledge sidebar tab is gated on a real OpenFGA capability, and the RAG server and BFF enforce deny-by-default. AgentGateway gains an MCP route bridge so platform MCP endpoints (including the built-in Knowledge Base server) can be rendered straight from Helm, and the default now routes all gateway-managed MCP servers through the gateway. Keycloak adds strict client-secret reconciliation for production installs and a migration-health panel in the admin UI, while a RAG ingestor SSRF fix and pinned TLS dependencies harden the web loader.

What's New

Knowledge Base & RAG Access Control

Complete RAG OpenFGA access model — adds knowledge-base sharing, per-resource gates, and RAG server/BFF enforcement, plus data_source and mcp_tool universal OpenFGA types and a BFF list filter; the Graph tab is gated on any-KB-readable and Knowledge sidebar tabs render per-tab gates with empty states (#1591)
Route capabilities in the canonical model — OpenFGA consolidates to a single canonical chart model artifact and adds organization route-capability relations for fine-grained application gates (#1592)
Deny-by-default cleanup — removes legacy RAG group fallback propagation from setup and migration docs so local and Helm installs stay aligned with deny-by-default OpenFGA behavior (#1601)

AgentGateway MCP Routing

MCP route bridge for RBAC runtimes — a config bridge syncs compose MCP routes, and Helm now renders MCP route targets including a built-in knowledgeBaseTarget and arbitrary extraMcpTargets (one AgentgatewayBackend + HTTPRoute per entry, /mcp/ → static host:port) (#1595)
Secret-backed backend auth env — new agentgateway.extraEnv / extraEnvFrom let the standalone AgentGateway config resolve backend-auth placeholders (e.g. GITHUB_PERSONAL_ACCESS_TOKEN, GITLAB_PERSONAL_ACCESS_TOKEN) from Kubernetes secrets (#1595)
CRD-free routing by default — new global.agentgateway.routingMode defaults to static, which renders the standalone proxy's config (one /mcp/ route/backend per target) instead of Gateway API/AgentGateway custom resources. Enabling AgentGateway therefore no longer requires the gateway.networking.k8s.io/agentgateway.dev CRDs or a controller, keeping helm diff/helm upgrade clean on clusters you do not own; MCP endpoints stay discoverable via the proxy admin /config endpoint consumed by the UI discover/sync flow. Set routingMode: gateway-api to opt back into the controller-managed Gateway data plane (#1629)

Authentication & Keycloak

Strict client-secret reconciliation — managed Keycloak client secrets are reconciled for production installs, with strict-secret test coverage and updated Slack bot Keycloak helper behavior (#1593)
Keycloak migration health surfaces — new migration-health summary APIs, an admin UI panel, and header/release signals for diagnosing realm migration state (#1597)
withAuth routes mapped to RBAC capabilities — protected BFF route groups now map to explicit OpenFGA capabilities and require Slack/Webex resource read access before returning access-check details (#1594)
Centralized local-dev auth bypass — a single dev-auth provider replaces the CAIPE_UNSAFE_RBAC_BYPASS checks that were scattered across the API middleware, RAG proxy, OpenFGA helpers, and admin/UI gates; the bypass admin principal is returned only when SSO_ENABLED=false, ALLOW_DEV_ADMIN_WHEN_SSO_DISABLED=true, and CAIPE_UNSAFE_RBAC_BYPASS=true are all set outside production (#1613)

Admin UI

Slack onboarding redesign — the admin Slack experience is reorganized into Configured / Onboard / Advanced tabs (#1613)
Hardened ReBAC assignment — ReBAC assignment operations in the admin UI are hardened and the OpenFGA inspector uses exact tuple filters (#1613)

AI Review

Overhauled review rubrics — the default AI Review rubric for agent system prompts expands from 7 to 11 criteria (adding negative-constraints, failure-mode-handling, prompt-injection-resistance, and more), and the SKILL.md rubric expands to 11 criteria emphasizing trigger conditions, actionable instructions, and bounded scope; weights now reflect real importance (#1608)

Configuration Defaults

Bedrock AI assist defaults to Claude Haiku 4.5 — local setup and AI assist fallbacks now default to Claude Haiku 4.5 on Bedrock; the stale Claude 3.5 Bedrock seed model is removed while Sonnet remains available as an explicit option (#1605)

Bug Fixes

dynamic-agents: forward caller bearer tokens through MCP httpx clients so user JWTs reach downstream MCP servers (#1598)
dynamic-agents: show an inline required-field message (with TeamPicker ARIA hooks) when creating a dynamic agent without an owner team (#1606)
credentials: align the OAuth service factory and Mongo envelope-store defaults (#1600)
keycloak: correctly type the management-permissions enabled flag (#1597)
setup-caipe: honor declined prompts — ENABLE_INGRESS=false and ENABLE_METALLB=false are now set when the user answers "No", instead of always installing both (#1587)
setup-caipe: use the native Anthropic model ID for Claude Haiku 4.5 — the previous -v1:0 Bedrock inference-profile suffix was rejected by the native Anthropic API (#1542)

Security

rag-ingestors: block SSRF by rejecting non-public web-loader start and redirect URLs, and pin Twisted for TLS compatibility, with regression coverage (#1599)

Breaking Changes

No breaking changes. Drop-in upgrade from 0.5.1.

Known Issues

None known at this time.

Upgrade

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.2 \
  -f your-values.yaml

Upgrade Guide: 0.5.1 → 0.5.2

Overview

0.5.2 is a drop-in upgrade — no values.yaml edits are required. The chart adds new optional AgentGateway routing keys (all with working defaults) and changes one default: gateway-managed MCP servers now route through AgentGateway by default. The bulk of the release is RAG/Knowledge Base OpenFGA access control and Keycloak hardening, none of which require values changes for existing deployments.

Helm Values Changes

No breaking Helm values changes between 0.5.1 and 0.5.2. The diff is limited to new optional AgentGateway keys and one changed default.

New Optional: AgentGateway MCP Routing

Key	Default	Description
`global.agentgateway.knowledgeBaseTarget.enabled`	`true`	Render a built-in Knowledge Base MCP route aligned with the RAG server MCP backend
`global.agentgateway.knowledgeBaseTarget.host`	`rag-server.{{ .Release.Namespace }}.svc.cluster.local`	Upstream host for the Knowledge Base MCP route
`global.agentgateway.knowledgeBaseTarget.port`	`9446`	Upstream port
`global.agentgateway.knowledgeBaseTarget.protocol`	`StreamableHTTP`	MCP transport protocol
`global.agentgateway.knowledgeBaseTarget.pathPrefix`	`/mcp/knowledge-base`	Route path prefix
`global.agentgateway.extraMcpTargets`	`[]`	Additional MCP routes not rendered from `agent-*` subcharts; one `AgentgatewayBackend` + `HTTPRoute` per entry
`agentgateway.extraEnv`	`[]`	Secret-backed env for backend-auth placeholders in the standalone AgentGateway config
`agentgateway.extraEnvFrom`	`[]`	`envFrom` sources for the AgentGateway container

These default to safe values; no action is required unless you want to route additional platform MCP endpoints or wire backend-auth secrets (e.g. GITHUB_PERSONAL_ACCESS_TOKEN).

Default Changed: AgentGateway MCP Server IDs

Affected key: dynamic-agents config AGENT_GATEWAY_MCP_SERVER_IDS

Before (0.5.1):

AGENT_GATEWAY_MCP_SERVER_IDS: "jira"

After (0.5.2):

AGENT_GATEWAY_MCP_SERVER_IDS: "all"

Action: None required. "all" only applies to gateway-managed MCP rows; manual/direct MCP rows keep their stored endpoint so tool names still reflect their real upstreams. If you previously relied on only Jira being routed through the shared AgentGateway backend, pin this back to "jira" (or your explicit list) in your dynamic-agents config.

Data Migrations

No MongoDB schema or data migrations required. The RAG OpenFGA access model and route capabilities are reconciled by the chart; deny-by-default behavior applies once the canonical model is loaded.

Upgrade Runbook

1. Update chart version

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.2 \
  -f your-values.yaml

2. (Optional) Pin AgentGateway MCP routing

If you do not want all gateway-managed MCP servers routed through AgentGateway, set AGENT_GATEWAY_MCP_SERVER_IDS back to an explicit list in your dynamic-agents config. To route extra platform MCP endpoints, populate global.agentgateway.extraMcpTargets.

3. Verify

kubectl get pods -n <namespace>

# Confirm the Knowledge Base MCP route / AgentGateway backend is healthy
kubectl get httproute -n <namespace> | grep mcp

Check that OpenFGA-gated Knowledge sidebar tabs and Graph access resolve as expected for your teams — KBs now require explicit sharing under deny-by-default.

Full Values Diff

Raw diff (0.5.1 → 0.5.2)

Release 0.5.3 — CRD-Free Gateway and Release-Name Defaults

2026-05-29T00:00:00.000Z

Released: 2026-05-29 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.3 Previous release: 0.5.2

Highlights

0.5.3 makes AgentGateway CRD-free by default. The new global.agentgateway.routingMode defaults to static, so enabling the gateway renders the standalone proxy's own config instead of Gateway API / AgentGateway custom resources — no cluster-scoped CRDs and no controller install required, which keeps helm diff and helm upgrade clean on clusters you do not own. The chart also stops hardcoding ai-platform-engineering-* service URLs: in-cluster defaults are now computed from the Helm release name in the deployment templates, so installs under a custom release name resolve their supervisor, Keycloak, OpenFGA, skill-scanner, and bot URLs correctly without manual overrides. Rounding out the release, every agent gains proper Kubernetes startup/liveness/readiness probe semantics, and a Twisted bump closes a DNS-compression DoS in the RAG web loader.

What's New

AgentGateway Routing

CRD-free static routing by default — global.agentgateway.routingMode now defaults to static, which writes MCP routes into the standalone AgentGateway proxy's static config (one /mcp/ route/backend per target) instead of rendering Gateway, HTTPRoute, AgentgatewayBackend, and AgentgatewayPolicy custom resources. Enabling AgentGateway therefore no longer depends on the gateway.networking.k8s.io / agentgateway.dev CRDs or a Gateway controller; MCP endpoints stay discoverable through the proxy admin /config endpoint that the CAIPE UI discover/sync flow reads. A new global.agentgateway.static.jwtAuth block adds optional listener-level JWT validation for the standalone proxy, and the UI recovers each MCP route path from the live pathPrefix shape. Set routingMode: gateway-api to opt back into the controller-managed Gateway data plane (#1629)

Helm Release-Name Defaults

Release-name-aware service URLs — in-cluster service URL defaults that were previously hardcoded to ai-platform-engineering-* (or a literal {{ .Release.Name }} string) are now left empty and computed from the actual Helm release name inside the deployment templates. This covers the supervisor (A2A_BASE_URL), Keycloak (KEYCLOAK_URL), OpenFGA (httpUrl / OPENFGA_HTTP), skill-scanner (SKILL_SCANNER_URL), the Slack and Webex bot admin APIs, the credential service, the SLIM endpoint, and the OpenFGA authz-bridge JWKS URL — so a helm install foo … resolves to foo-keycloak, foo-openfga, and so on instead of silently pointing at the wrong service. Realm URL defaults also honor KEYCLOAK_REALM instead of a hardcoded caipe (#1612)

Health & Probes

Real Kubernetes probe semantics across agents — agents migrate from TCP to HTTP probes and gain startup probes; the supervisor registers /health and /ready routes on the A2A app, dynamic-agents and rag-server get corrected liveness semantics, skill-scanner and langgraph-redis get startup probes, and readiness endpoints now return HTTP 503 when their dependencies are unavailable so traffic is held off until a pod is genuinely ready (#1468)

Docs

Versioned docs generated at build time — the documentation site now materializes versioned docs from release tags at build time rather than committing versioned_docs/ trees, and the RBAC reference's broken anchor and unreadable draw.io SVGs are repaired

Bug Fixes

ui: recover the AgentGateway MCP route path from the live pathPrefix shape so discovered routes match the proxy config (#1629)
helm: wire the CAIPE UI to the AgentGateway proxy for CRD-free MCP discovery (#1629)
helm: fix whitespace trimming that caused YAML parse errors in deployment env blocks and compute release-name service URL defaults in templates (#1612)
ui: collapse the top bar on narrow screens and label the collapsed nav menu

Security

rag: bump Twisted to 26.4.0 to close a DNS-compression denial-of-service in the web loader
deps: bump PyJWT from 2.10.1 to 2.13.0 in the OpenFGA authz bridge, and force uuid >= 11.1.1 via overrides in the UI and docs builds

Breaking Changes

AgentGateway routing defaults to static (CRD-free). If you run with global.agentgateway.enabled: true and rely on the chart rendering Gateway API / AgentGateway custom resources (the controller-managed data plane), you must now set global.agentgateway.routingMode: gateway-api explicitly. With the default global.agentgateway.enabled: false, there is no impact.

Known Issues

None known at this time.

Upgrade

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.3 \
  -f your-values.yaml

Upgrade Guide: 0.5.2 → 0.5.3

Overview

For a stock deployment — default release name ai-platform-engineering, AgentGateway disabled — 0.5.3 is a drop-in upgrade. Two things are worth knowing before you upgrade: the AgentGateway routingMode default flipped to static, and many in-cluster service URL defaults are now computed from the Helm release name instead of being hardcoded. Neither changes behavior for the default release name, but both matter if you enable AgentGateway or run under a custom release name.

Helm Values Changes

Behavioral Change: AgentGateway `routingMode`

Affected key: global.agentgateway.routingMode (new key, defaults to static)

Before (0.5.2): enabling AgentGateway rendered Gateway API / AgentGateway custom resources (required the CRDs + a controller).

After (0.5.3):

global:
  agentgateway:
    enabled: true
    routingMode: static   # NEW default — no CRDs, no controller

Action: If you depend on the controller-managed Gateway data plane (Gateway API CRs), set routingMode: gateway-api explicitly. Otherwise no action — static requires no CRDs and keeps helm upgrade clean.

Changed Defaults: Release-Name Service URLs

A set of service URL keys changed their default from a literal ai-platform-engineering-* / {{ .Release.Name }} string to an empty string (""), because the value is now rendered from .Release.Name in the deployment templates. Affected keys include global.slim.endpoint, global.openfga.httpUrl, CAIPE UI A2A_BASE_URL / SKILL_SCANNER_URL / SLACK_BOT_ADMIN_URL / WEBEX_BOT_ADMIN_URL, dynamic-agents KEYCLOAK_URL / OPENFGA_HTTP / CREDENTIAL_API_URL, the Slack/Webex bot CAIPE_API_URL, the Webex admin issuer/JWKS URLs, and the OpenFGA authz-bridge httpUrl / tokenValidation.jwksUrl.

Action:

Default release name (ai-platform-engineering): none — the rendered value is identical to the old hardcoded default.
Custom release name: you can now remove any manual overrides you previously added to point these at -…; the empty default resolves correctly on its own.
If you explicitly set any of these to an external endpoint, your override is preserved.

New Optional Fields

Key	Default	Description
`global.agentgateway.static.jwtAuth.enabled`	`false`	Listener-level JWT validation for the standalone proxy (static routing mode)
`global.agentgateway.static.jwtAuth.issuer` / `jwksUrl` / `audiences`	`""` / `""` / `[]`	JWT issuer, JWKS URL, and audiences for the static listener policy
`dynamic-agents` `OPENFGA_HTTP`	`""` (release-name default)	OpenFGA HTTP endpoint for dynamic-agents authorization
`dynamic-agents` `OPENFGA_STORE_NAME`	`caipe-openfga`	OpenFGA store name for dynamic-agents

Data Migrations

No MongoDB schema or data migrations are required.

Upgrade Runbook

1. Update chart version

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.3 \
  -f your-values.yaml

2. (Only if you use AgentGateway with CRDs) Pin routing mode

global:
  agentgateway:
    enabled: true
    routingMode: gateway-api

3. Verify

kubectl get pods -n <namespace>

# Probes are stricter now — confirm pods reach Ready and stay there
kubectl get pods -n <namespace> -o wide

If AgentGateway is enabled in static mode, confirm MCP routes resolve through the proxy admin /config endpoint (the UI discover/sync flow reads from there) rather than expecting HTTPRoute objects.

Full Values Diff

Raw diff (0.5.2 → 0.5.3)

Release 0.5.4 — Admin UI Polish and Keycloak Realm Fix

2026-05-29T00:00:00.000Z

Released: 2026-05-29 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.4 Previous release: 0.5.3

Highlights

0.5.4 is a small maintenance release focused on admin UI consistency and a Keycloak fix. Native agent and team elements are replaced with the shared searchable picker components, and the Slack (SlackChannelRebacPanel) and Webex (WebexSpaceRebacPanel) admin panels are DRYed up into one shared ConnectorAdminPanel, giving both connectors identical ReBAC management UX (#1632)

Team card resource counts — team cards now show knowledge-base, agent, and tool counts so admins can see a team's footprint without opening it (#1643)

Bug Fixes

admin: point the team Knowledge tab create links at /knowledge-bases instead of a stale route (#1643)
keycloak: render the configured realm name instead of the hardcoded caipe default (#1657)
compose: remove a duplicate volumes key in the openfga-init service that broke docker compose parsing (#1638)

Security

No security-specific changes in this release.

Breaking Changes

No breaking changes. Drop-in upgrade from 0.5.3.

Known Issues

None known at this time.

Upgrade

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.4 \
  -f your-values.yaml

Upgrade Guide: 0.5.3 → 0.5.4

Overview

0.5.4 is a drop-in upgrade — no values.yaml edits are required. The release is limited to UI refactors, two admin fixes, a Keycloak realm-name fix, and a Docker Compose parsing fix. There are no chart value changes.

Helm Values Changes

No Helm values changes between 0.5.3 and 0.5.4. The helm show values output is byte-for-byte identical.

Data Migrations

No MongoDB schema or data migrations are required.

Upgrade Runbook

1. Update chart version

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.4 \
  -f your-values.yaml

2. Verify

kubectl get pods -n <namespace>

If you run Keycloak under a non-caipe realm name, confirm the admin UI and bot integrations now reflect the configured realm.

Full Values Diff

No Helm values changes between 0.5.3 and 0.5.4 — drop-in upgrade.

Release 0.5.1 — Fine-Grained Knowledge Base RBAC

2026-05-27T00:00:00.000Z

Released: 2026-05-27 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.1 Previous release: 0.5.0

Highlights

0.5.1 makes OpenFGA the source of truth for human access to the RAG knowledge base surfaces — Search, Data Sources, Graph, and MCP Tools — and lets admins share individual knowledge bases with teams through relationship-based grants. Under the hood, team membership is consolidated into a single canonical store so every reader and writer agrees on who belongs to a team, eliminating the drift that caused authorized users to fall back to the Default CAIPE Supervisor instead of their configured agent. The release also adds a searchable team picker across admin panels, a friendlier first-run experience that seeds a working Hello-World agent, and an intentionally noisy emergency flag to bypass UI RBAC while repairing an OpenFGA/Keycloak stack.

What's New

Fine-Grained Knowledge Base Access Control

OpenFGA-backed KB access — Search, Data Sources, Graph, and MCP Tools now resolve human access through OpenFGA instead of legacy role/group/trusted-network checks, making one consistent decision across the UI, BFF, and RAG server (#1584)
Share knowledge bases with teams — admins can grant teams access to individual knowledge bases through an OpenFGA reconciler with backfill for already-shared KBs (#1584)
New data_source and mcp_tool resource types — added as first-class OpenFGA types with BFF list filtering, so users only see the data sources and tools they can actually use (#1584)
Per-tab Knowledge sidebar gates — each Knowledge tab is gated on the relevant OpenFGA relation with empty states instead of access-denied dead ends; the Graph tab unlocks when any KB is readable (#1584)
Explicit org-admin super-grant — org admins keep access to KB, Search, Data Sources, Graph, and MCP Tools, including the grant needed to create a datasource before its ownership tuples exist (#1584)

Canonical Team Membership & Onboarding

Single source of truth for membership — the duplicate teams.members[] array is retired in favor of the canonical team_membership_sources collection; every auth gate, API consumer, and admin view now reads from it, and GET /api/admin/teams returns a canonical member_count (#1583)
Searchable team picker — new TeamPicker and TeamMultiPicker components replace native

CAIPE Blog

Release 0.5.8 — Skills FGA, catalog API keys BFF, and RBAC migrations

Highlights​

What's New​

Skills and catalog​

RBAC​

Breaking Changes​

Catalog API key hash​

Security​

Known Issues​

Upgrade​

Upgrade Guide: 0.5.4 → 0.5.8​

Overview​

Catalog API key hash​

1. Confirm pepper is set consistently​

2. Rotate keys​

3. Verify​

Helm Values Changes​

Data Migrations​

Upgrade Runbook​

1. Rotate catalog API keys (if used)​

2. Update chart version​

3. Run ReBAC migrations​

4. Verify​

Release 0.5.2 — RAG Access Control and Gateway Routing

Highlights​

What's New​

Knowledge Base & RAG Access Control​

AgentGateway MCP Routing​

Authentication & Keycloak​

Admin UI​

AI Review​

Configuration Defaults​

Bug Fixes​

Security​

Breaking Changes​

Known Issues​

Upgrade​

Upgrade Guide: 0.5.1 → 0.5.2​

Overview​

Helm Values Changes​

New Optional: AgentGateway MCP Routing​

Default Changed: AgentGateway MCP Server IDs​

Data Migrations​

Upgrade Runbook​

1. Update chart version​

2. (Optional) Pin AgentGateway MCP routing​

3. Verify​

Full Values Diff​

Release 0.5.3 — CRD-Free Gateway and Release-Name Defaults

Highlights​

What's New​

AgentGateway Routing​

Helm Release-Name Defaults​

Health & Probes​

Docs​

Bug Fixes​

Security​

Breaking Changes​

Known Issues​

Upgrade​

Upgrade Guide: 0.5.2 → 0.5.3​

Overview​

Helm Values Changes​

Behavioral Change: AgentGateway routingMode​

Changed Defaults: Release-Name Service URLs​

New Optional Fields​

Data Migrations​

Upgrade Runbook​

1. Update chart version​

2. (Only if you use AgentGateway with CRDs) Pin routing mode​

3. Verify​

Full Values Diff​

Release 0.5.4 — Admin UI Polish and Keycloak Realm Fix

Highlights​

Bug Fixes​

Security​

Breaking Changes​

Known Issues​

Upgrade​

Highlights

What's New

Skills and catalog

RBAC

Breaking Changes

Catalog API key hash

Security

Known Issues

Upgrade

Upgrade Guide: 0.5.4 → 0.5.8

Overview

Catalog API key hash

1. Confirm pepper is set consistently

2. Rotate keys

3. Verify

Helm Values Changes

Data Migrations

Upgrade Runbook

1. Rotate catalog API keys (if used)

2. Update chart version

3. Run ReBAC migrations

4. Verify

Highlights

What's New

Knowledge Base & RAG Access Control

AgentGateway MCP Routing

Authentication & Keycloak

Admin UI

AI Review

Configuration Defaults

Bug Fixes

Security

Breaking Changes

Known Issues

Upgrade

Upgrade Guide: 0.5.1 → 0.5.2

Overview

Helm Values Changes

New Optional: AgentGateway MCP Routing

Default Changed: AgentGateway MCP Server IDs

Data Migrations

Upgrade Runbook

1. Update chart version

2. (Optional) Pin AgentGateway MCP routing

3. Verify

Full Values Diff

Highlights

What's New

AgentGateway Routing

Helm Release-Name Defaults

Health & Probes

Docs

Bug Fixes

Security

Breaking Changes

Known Issues

Upgrade

Upgrade Guide: 0.5.2 → 0.5.3

Overview

Helm Values Changes

Behavioral Change: AgentGateway `routingMode`

Changed Defaults: Release-Name Service URLs

New Optional Fields

Data Migrations

Upgrade Runbook

1. Update chart version

2. (Only if you use AgentGateway with CRDs) Pin routing mode

3. Verify

Full Values Diff

Highlights

Bug Fixes

Security

Breaking Changes

Known Issues

Upgrade

Upgrade Guide: 0.5.3 → 0.5.4

Overview

Helm Values Changes

Data Migrations

Upgrade Runbook