Add shared/multi-tenant cluster note (oidc-reviewer collision)

platform/hosting/self-managed/operator.mdx

@@ -330,6 +330,20 @@ After the MCP server is healthy, configure your MCP client to use `https://<HOST
 
 Kubernetes is the same whether it runs on-premises or in the cloud. The main differences are in naming and managed services (for example, MySQL compared to RDS, or S3 compared to on-premises object storage). This section covers considerations that vary by environment.
 
+### Shared or multi-tenant clusters
+
+If you run more than one W&B install on the same cluster, give each one a unique release (CR) name. The chart creates some cluster-scoped objects named after the release, such as the `<release>-oidc-reviewer` ClusterRoleBinding. If two installs use the same release name, the second one fails with an ownership error like:
+
+```text
+ClusterRoleBinding "wandb-oidc-reviewer" ... cannot be imported into the current release:
+... annotation validation error: key "meta.helm.sh/release-namespace" must equal ...
+```
+
+To avoid this on a shared cluster:
+
+- Use a unique release (CR) name for each install (for example `wandb-team-a`, not `wandb`).
+- Set `app.internalJWTMap: []` unless you need internal JWT mapping, such as native-Kubernetes-OIDC on-premises installs that rely on the `oidc-reviewer` binding. This skips rendering the `oidc-reviewer` ClusterRoleBinding.
+
 ### On-premises and bare metal
 
 When deploying to on-premises or bare-metal Kubernetes, pay attention to the following.
@@ -1239,13 +1253,13 @@ Self-Managed deployments that use an external ClickHouse cluster must verify Cli
 
 ### Unsupported ClickHouse versions
 
-W&B Self-Managed deployments using W&B Weave or Models OLAP features require a supported version of both ClickHouse Server and ClickHouse Keeper.
-
-- Weave does not work with ClickHouse 26.1 or 26.2.
-- The Models OLAP features described in the next section require ClickHouse 26.2+.
-- Deployments using both Weave and Models OLAP features require ClickHouse 26.3.
-
-If your W&B Self-Managed deployment uses neither Weave nor Models OLAP features, ClickHouse is not required.
+W&B Self-Managed deployments using W&B Weave or Models OLAP features require a supported version of both ClickHouse Server and ClickHouse Keeper.
+
+- Weave does not work with ClickHouse 26.1 or 26.2.
+- The Models OLAP features described in the next section require ClickHouse 26.2+.
+- Deployments using both Weave and Models OLAP features require ClickHouse 26.3.
+
+If your W&B Self-Managed deployment uses neither Weave nor Models OLAP features, ClickHouse is not required.
 
 
 ### Models OLAP features