You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/userguide.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -111,11 +111,12 @@ See the [Cluster Registration documentation](./cluster-registration.md) for more
111
111
You can enable federation of any Kubernetes API type (including CRDs) by using the
112
112
`kubefedctl` command as follows.
113
113
114
-
**NOTE:** Federation of a CRD requires that the CRD be installed on all member clusters. If
115
-
the CRD is not installed on a member cluster, propagation to that cluster will fail.
114
+
**NOTE:** Federation of a CRD requires that the CRD Kubernetes type (`customresourcedefinitions`) to be enabled, to then
115
+
federate any custom CRD on the member clusters. If the CRD Kubernetes type is not enabled and its Federated equivalent CRD is not federated, the propagation to that cluster will fail.
116
116
117
117
```bash
118
-
kubefedctl enable<target kubernetes API type>
118
+
kubefedctl enable customresourcedefinitions
119
+
kubefedctl federate crd <target kubernetes API type># <target kubernetes API type> = mytype.mygroup.mydomain.io
119
120
```
120
121
121
122
The `<target kubernetes API type>` can be any of the following
0 commit comments