Add multi-cluster deployment guide for Knative Operator

docs/versioned/.nav.yml

@@ -250,6 +250,7 @@ nav:
           - Configuring Knative using the Operator: install/operator/configuring-with-operator.md
           - Configuring Knative Serving CRDs: install/operator/configuring-serving-cr.md
           - Configuring Knative Eventing CRDs: install/operator/configuring-eventing-cr.md
+          - Deploy Knative to a remote cluster: install/operator/multi-cluster-deployment.md
         - Installing plugins:
           - Install Istio for Knative: install/installing-istio.md
           # TODO: docs for kourier, contour, gateway-api

docs/versioned/install/operator/configuring-eventing-cr.md

@@ -301,6 +301,35 @@ spec:
   defaultBrokerClass: MTChannelBasedBroker
 ```
 
+## Deploy Knative Eventing to a remote cluster
+
+Starting with Knative Operator v1.22, you can target a remote cluster by
+setting `spec.clusterProfileRef` on the `KnativeEventing` CR. The Operator
+resolves the referenced `ClusterProfile`, deploys Knative Eventing components
+on that cluster, and manages their lifecycle through the same CR on the hub.
+
+```yaml
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeEventing
+metadata:
+  name: knative-eventing
+  namespace: knative-eventing
+spec:
+  clusterProfileRef:
+    name: spoke-cluster-1
+    namespace: fleet-system
+```
+
+Before applying this CR, enable multi-cluster support on the Operator and
+register the spoke as a `ClusterProfile`. See
+[Deploy Knative to a remote cluster](multi-cluster-deployment.md) for the
+complete procedure.
+
+!!! important
+    `spec.clusterProfileRef` is immutable. To move a `KnativeEventing`
+    resource between clusters, delete it and re-create it with the new
+    reference.
+
 ## High availability
 
 By default, Knative Eventing runs a single instance of each deployment. The `spec.high-availability` field allows you to configure the number of replicas for all deployments managed by the operator.

docs/versioned/install/operator/configuring-serving-cr.md

@@ -574,6 +574,38 @@ spec:
       enabled: true
 ```
 
+## Deploy Knative Serving to a remote cluster
+
+Starting with Knative Operator v1.22, you can target a remote cluster by
+setting `spec.clusterProfileRef` on the `KnativeServing` CR. The Operator
+resolves the referenced `ClusterProfile`, deploys Knative Serving components
+on that cluster, and manages their lifecycle through the same CR on the hub.
+
+```yaml
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  clusterProfileRef:
+    name: spoke-cluster-1
+    namespace: fleet-system
+  ingress:
+    kourier:
+      enabled: true
+```
+
+Before applying this CR, enable multi-cluster support on the Operator and
+register the spoke as a `ClusterProfile`. See
+[Deploy Knative to a remote cluster](multi-cluster-deployment.md) for the
+complete procedure.
+
+!!! important
+    `spec.clusterProfileRef` is immutable. To move a `KnativeServing`
+    resource between clusters, delete it and re-create it with the new
+    reference.
+
 ## High availability
 
 By default, Knative Serving runs a single instance of each deployment. The `spec.high-availability` field allows you to configure the number of replicas for all deployments managed by the operator.

docs/versioned/install/operator/configuring-with-operator.md

@@ -19,6 +19,11 @@ All Knative ConfigMaps are created in the same namespace as the custom resource
 
 The `spec.config` in the Knative custom resources have one `<name>` entry for each ConfigMap, named `config-<name>`, with a value which is be used for the ConfigMap `data`.
 
+To deploy Knative components to a remote Kubernetes cluster from this
+Operator, set `spec.clusterProfileRef` on the CR. For configuration details,
+prerequisites, and operational guidance, see
+[Deploy Knative to a remote cluster](multi-cluster-deployment.md).
+
 ## Examples
 
 You can specify that the `KnativeServing` custom resource uses the `config-domain` ConfigMap  as follows:

docs/versioned/install/operator/knative-with-operators.md

@@ -61,6 +61,12 @@ To see available values, run:
 helm show values -n knative-operator knative-operator/knative-operator
 ```
 
+!!! note
+    To deploy Knative components to remote clusters from this Operator,
+    enable multi-cluster support through the `knative_operator.multicluster.*`
+    Helm values. For prerequisites and configuration details, see
+    [Deploy Knative to a remote cluster](multi-cluster-deployment.md).
+
 ### Verify your Knative Operator installation
 
 1. Because the Operator is installed to the `knative-operator` namespace, ensure you set the current namespace to `default` by running the command: