Skip to main content
September 3, 2026 Documentation correction Action required

Affects


Teams operating Streaming Hub in SaaS multi-tenant mode.

What changed


The multi-tenant control-plane roster comes from Tenant Manager, with Redis lifecycle updates and periodic refresh. Each ingest-capable replica uses the deployment-level STREAMING_HUB_KAFKA_* connection; it does not resolve Kafka credentials through the Secrets Manager sweep. Secrets Manager remains the source for per-tenant M2M credentials used to discover authenticated producer manifests. Multi-tenant deployments also require the Tenant Manager and Redis configuration documented in the environment reference. This corrects the documented configuration contract for current runtime behavior; it does not announce a runtime release.

Impact


Classification: Action required.

What you need to do


1
Review multi-tenant deployments for the Tenant Manager, Redis, and deployment-level Kafka configuration. Keep producer-manifest M2M credentials in Secrets Manager.

Deadline

Update before the next multi-tenant Streaming Hub deployment.