diff --git a/docs/blog/articles/deploying-knative-to-remote-clusters-with-operator.md b/docs/blog/articles/deploying-knative-to-remote-clusters-with-operator.md
index 8dfa40300c..898b82f2cd 100644
--- a/docs/blog/articles/deploying-knative-to-remote-clusters-with-operator.md
+++ b/docs/blog/articles/deploying-knative-to-remote-clusters-with-operator.md
@@ -18,7 +18,7 @@ Platform teams often manage more than one Kubernetes cluster. Some clusters are
 
 Starting with Knative Operator v1.22, a single Operator can deploy Knative components to a different Kubernetes cluster. The cluster that runs the Operator acts as the **hub cluster**. The cluster that receives Knative Serving or Knative Eventing acts as a **spoke cluster**. You select the spoke by setting `spec.clusterProfileRef` on the `KnativeServing` or `KnativeEventing` custom resource.
 
-This feature uses the SIG-Multicluster Cluster Inventory API, introduced through [KEP-5339](https://github.com/kubernetes/enhancements/issues/5339). The Operator reads a `ClusterProfile` resource to discover the remote cluster endpoint and access provider, then runs the normal Knative installation pipeline against that remote cluster.
+This feature uses the SIG-Multicluster Cluster Inventory API `v1alpha1`, introduced through [KEP-5339](https://github.com/kubernetes/enhancements/issues/5339). The Operator reads a `ClusterProfile` resource to discover the remote cluster endpoint and access provider, then runs the normal Knative installation pipeline against that remote cluster.
 
 If `spec.clusterProfileRef` is not set, nothing changes. The Operator keeps deploying Knative to the local cluster exactly as it did before.
 
@@ -37,7 +37,7 @@ This is useful when you want to:
 The feature is intentionally based on the Cluster Inventory API instead of a specific fleet manager. A fleet system such as Open Cluster Management can publish the `ClusterProfile` resources, and proof-of-concept environments can register them manually.
 
 !!! important
-    Multi-cluster deployment is a beta feature in Knative Operator v1.22 and later. It depends on the SIG-Multicluster Cluster Inventory API, which is still in alpha. The API schema and recommended access provider plugins might change between releases.
+    Multi-cluster deployment is an alpha feature in Knative Operator v1.22 and later and is disabled by default. The Cluster Inventory API schema and recommended access provider plugins might change between releases.
 
 ## How the Operator targets a remote cluster
 
diff --git a/docs/versioned/install/operator/multi-cluster-deployment.md b/docs/versioned/install/operator/multi-cluster-deployment.md
index f5339497f8..1372e6f1ae 100644
--- a/docs/versioned/install/operator/multi-cluster-deployment.md
+++ b/docs/versioned/install/operator/multi-cluster-deployment.md
@@ -8,15 +8,14 @@ function: how-to
 
 # Deploy Knative to a remote cluster
 
+**Stage**: Alpha, disabled by default
+
 Starting with Knative Operator v1.22, a single Operator can deploy Knative Serving or Knative Eventing to a different Kubernetes cluster. The cluster that runs the Operator is the **hub cluster**, and the cluster that receives the Knative components is a **spoke cluster**. You set the field `spec.clusterProfileRef` on the `KnativeServing` or `KnativeEventing` CR to point to a `ClusterProfile` resource that describes a spoke cluster.
 
-The Operator resolves the referenced `ClusterProfile` through the SIG-Multicluster Cluster Inventory API ([KEP-5339](https://github.com/kubernetes/enhancements/issues/5339)), so the feature works with any fleet manager that publishes `ClusterProfile` resources, such as Open Cluster Management or MultiKueue. You can also register `ClusterProfile` resources manually for proof-of-concept work.
+The Operator resolves the referenced `ClusterProfile` through the SIG-Multicluster Cluster Inventory API `v1alpha1` ([KEP-5339](https://github.com/kubernetes/enhancements/issues/5339)), so the feature works with any fleet manager that publishes `ClusterProfile` resources, such as Open Cluster Management or MultiKueue. You can also register `ClusterProfile` resources manually for proof-of-concept work. The Cluster Inventory API schema and recommended access provider plugins might change between releases.
 
 If `spec.clusterProfileRef` is not set on a CR, the Operator deploys components to the local cluster, exactly as in earlier releases.
 
-!!! important
-    Multi-cluster deployment is a beta feature in Knative Operator v1.22 and later. This feature depends on the SIG-Multicluster Cluster Inventory API, which is still in alpha; its schema and recommended access provider plugins might change between releases.
-
 ## Overview
 
 A multi-cluster deployment runs the reconciliation loop on the hub and applies resources on a spoke. When you create or update a CR with `spec.clusterProfileRef`, the Operator performs the following steps: