CR conversion

content/en/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning.md

@@ -11,14 +11,9 @@ weight: 30
 {{% capture overview %}}
 This page explains how to add versioning information to
 [CustomResourceDefinitions](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#customresourcedefinition-v1beta1-apiextensions), to indicate the stability
-level of your CustomResourceDefinitions. It also describes how to upgrade an
+level of your CustomResourceDefinitions or advance your API to a new version with conversion between them. It also describes how to upgrade an
 object from one version to another.
 
-{{< note >}}
-**Note**: All specified versions must use the same schema. The is no schema
-conversion between versions.
-{{< /note >}}
-
 {{% /capture %}}
 
 {{% capture prerequisites %}}
@@ -199,4 +194,14 @@ to `v1`.
 3.  Update the CustomResourceDefinition `Status` by removing `v1beta1` from
     `storedVersions` field.
 
+## Custom conversion between versions
+
+By default, the assumption is that all versions share the same schema. When advancing an API,
+this is not normally the case. That's why CustomResourceDefinition supports conversion using
+an external webhook. This conversion happens whenever a different version is requested from the
+stored version or when the provided object is not in the sotre version.
+
+TODO: Add Conversion document here.
+
+
 {{% /capture %}}