Updates the ControllerConfig deprecation warning (#548)

content/master/concepts/providers.md

@@ -15,6 +15,7 @@ providing
 logic for any external resources.
 
 Examples of providers include:
+
 * [Provider AWS](https://github.com/upbound/provider-aws)
 * [Provider Azure](https://github.com/upbound/provider-azure)
 * [Provider GCP](https://github.com/upbound/provider-gcp)
@@ -169,6 +170,7 @@ install times.
 The Crossplane community has more
 [details on scaling CRDs](https://github.com/crossplane/crossplane/blob/master/design/one-pager-crd-scaling.md).
 {{< /hint >}}
+
 ### Provider conditions
 
 Crossplane uses a standard set of `Conditions` for Providers.  
@@ -193,16 +195,20 @@ Status:
 ```
 
 #### Types
+
 Provider `Conditions` support two `Types`:
+
 * `Type: Installed` - the Provider package installed but isn't ready for use.
 * `Type: Healthy` - The Provider package is ready to use.
 
 #### Reasons
+
 Each `Reason` relates to a specific `Type` and `Status`. Crossplane uses the
 following `Reasons` for Provider `Conditions`.
 
 <!-- vale Google.Headings = NO -->
 ##### InactivePackageRevision
+
 `Reason: InactivePackageRevision` indicates the Provider Package is using an
 inactive Provider Package Revision.
 
@@ -233,6 +239,7 @@ Reason: ActivePackageRevision
 
 <!-- vale Google.Headings = NO -->
 ##### HealthyPackageRevision
+
 The Provider is fully installed and ready to use.
 
 {{<hint "tip" >}}
@@ -267,7 +274,6 @@ Reason: UnhealthyPackageRevision
 ##### UnknownPackageRevisionHealth
 <!-- vale Google.Headings = YES -->
 
-
 The status of the Provider Package Revision is `Unknown`. The Provider Package
 Revision may be installing or has an issue.
 
@@ -285,6 +291,7 @@ Reason: UnknownPackageRevisionHealth
 ## Configure a Provider
 
 Providers have two different types of configurations:
+
 * _Controller configurations_ that change the settings of the Provider pod
   running inside the Kubernetes cluster. For example, Pod `toleration`.
 * _Provider configurations_ that change settings used when communicating with
@@ -297,12 +304,17 @@ Apply `ProviderConfig` objects to managed resources.
 {{< /hint >}}
 
 ### Controller configuration
+
 {{< hint "important" >}}
-The Crossplane community deprecated the `ControllerConfig` type in v1.11.
+The Crossplane community deprecated the `ControllerConfig` type in v1.11 to
+indicate that no further enhancements will be made to it.
 Applying a Controller configuration generates a deprecation warning.
 
 Controller configurations are still supported until there is a replacement type
-in a future Crossplane version.
+in a future Crossplane version. You can read more about the design of
+[Package Runtime Config](https://github.com/crossplane/crossplane/blob/master/design/one-pager-package-runtime-config.md)
+which will replace it in the future.
+
 {{< /hint >}}
 
 Applying a Crossplane `ControllerConfig` to a Provider changes the settings of
@@ -433,4 +445,3 @@ spec:
   providerConfigRef:
     name: admin-keys
 ```
-

content/v1.11/concepts/providers.md

@@ -14,6 +14,7 @@ providing
 logic for any external resources.
 
 Examples of providers include:
+
 * [Provider AWS](https://github.com/upbound/provider-aws)
 * [Provider Azure](https://github.com/upbound/provider-azure)
 * [Provider GCP](https://github.com/upbound/provider-gcp)
@@ -170,6 +171,7 @@ install times.
 The Crossplane community has more
 [details on scaling CRDs](https://github.com/crossplane/crossplane/blob/master/design/one-pager-crd-scaling.md).
 {{< /hint >}}
+
 ### Provider conditions
 
 Crossplane uses a standard set of `Conditions` for Providers.  
@@ -194,16 +196,20 @@ Status:
 ```
 
 #### Types
+
 Provider `Conditions` support two `Types`:
+
 * `Type: Installed` - the Provider package installed but isn't ready for use.
 * `Type: Healthy` - The Provider package is ready to use.
 
 #### Reasons
+
 Each `Reason` relates to a specific `Type` and `Status`. Crossplane uses the
 following `Reasons` for Provider `Conditions`.
 
 <!-- vale Google.Headings = NO -->
 ##### InactivePackageRevision
+
 `Reason: InactivePackageRevision` indicates the Provider Package is using an
 inactive Provider Package Revision.
 
@@ -234,6 +240,7 @@ Reason: ActivePackageRevision
 
 <!-- vale Google.Headings = NO -->
 ##### HealthyPackageRevision
+
 The Provider is fully installed and ready to use.
 
 {{<hint "tip" >}}
@@ -268,7 +275,6 @@ Reason: UnhealthyPackageRevision
 ##### UnknownPackageRevisionHealth
 <!-- vale Google.Headings = YES -->
 
-
 The status of the Provider Package Revision is `Unknown`. The Provider Package
 Revision may be installing or has an issue.
 
@@ -286,6 +292,7 @@ Reason: UnknownPackageRevisionHealth
 ## Configure a Provider
 
 Providers have two different types of configurations:
+
 * _Controller configurations_ that change the settings of the Provider pod
   running inside the Kubernetes cluster. For example, Pod `toleration`.
 * _Provider configurations_ that change settings used when communicating with
@@ -298,12 +305,16 @@ Apply `ProviderConfig` objects to managed resources.
 {{< /hint >}}
 
 ### Controller configuration
+
 {{< hint "important" >}}
-The Crossplane community deprecated the `ControllerConfig` type in v1.11.
+The Crossplane community deprecated the `ControllerConfig` type in v1.11 to
+indicate that no further enhancements will be made to it.
 Applying a Controller configuration generates a deprecation warning.
 
 Controller configurations are still supported until there is a replacement type
-in a future Crossplane version.
+in a future Crossplane version. You can read more about the design of
+[Package Runtime Config](https://github.com/crossplane/crossplane/blob/master/design/one-pager-package-runtime-config.md)
+which will replace it in the future.
 {{< /hint >}}
 
 Applying a Crossplane `ControllerConfig` to a Provider changes the settings of
@@ -434,4 +445,3 @@ spec:
   providerConfigRef:
     name: admin-keys
 ```
-

content/v1.12/concepts/providers.md

@@ -14,6 +14,7 @@ providing
 logic for any external resources.
 
 Examples of providers include:
+
 * [Provider AWS](https://github.com/upbound/provider-aws)
 * [Provider Azure](https://github.com/upbound/provider-azure)
 * [Provider GCP](https://github.com/upbound/provider-gcp)
@@ -170,6 +171,7 @@ install times.
 The Crossplane community has more
 [details on scaling CRDs](https://github.com/crossplane/crossplane/blob/master/design/one-pager-crd-scaling.md).
 {{< /hint >}}
+
 ### Provider conditions
 
 Crossplane uses a standard set of `Conditions` for Providers.  
@@ -194,16 +196,20 @@ Status:
 ```
 
 #### Types
+
 Provider `Conditions` support two `Types`:
+
 * `Type: Installed` - the Provider package installed but isn't ready for use.
 * `Type: Healthy` - The Provider package is ready to use.
 
 #### Reasons
+
 Each `Reason` relates to a specific `Type` and `Status`. Crossplane uses the
 following `Reasons` for Provider `Conditions`.
 
 <!-- vale Google.Headings = NO -->
 ##### InactivePackageRevision
+
 `Reason: InactivePackageRevision` indicates the Provider Package is using an
 inactive Provider Package Revision.
 
@@ -234,6 +240,7 @@ Reason: ActivePackageRevision
 
 <!-- vale Google.Headings = NO -->
 ##### HealthyPackageRevision
+
 The Provider is fully installed and ready to use.
 
 {{<hint "tip" >}}
@@ -268,7 +275,6 @@ Reason: UnhealthyPackageRevision
 ##### UnknownPackageRevisionHealth
 <!-- vale Google.Headings = YES -->
 
-
 The status of the Provider Package Revision is `Unknown`. The Provider Package
 Revision may be installing or has an issue.
 
@@ -286,6 +292,7 @@ Reason: UnknownPackageRevisionHealth
 ## Configure a Provider
 
 Providers have two different types of configurations:
+
 * _Controller configurations_ that change the settings of the Provider pod
   running inside the Kubernetes cluster. For example, Pod `toleration`.
 * _Provider configurations_ that change settings used when communicating with
@@ -298,12 +305,16 @@ Apply `ProviderConfig` objects to managed resources.
 {{< /hint >}}
 
 ### Controller configuration
+
 {{< hint "important" >}}
-The Crossplane community deprecated the `ControllerConfig` type in v1.11.
+The Crossplane community deprecated the `ControllerConfig` type in v1.11 to
+indicate that no further enhancements will be made to it.
 Applying a Controller configuration generates a deprecation warning.
 
 Controller configurations are still supported until there is a replacement type
-in a future Crossplane version.
+in a future Crossplane version. You can read more about the design of
+[Package Runtime Config](https://github.com/crossplane/crossplane/blob/master/design/one-pager-package-runtime-config.md)
+which will replace it in the future.
 {{< /hint >}}
 
 Applying a Crossplane `ControllerConfig` to a Provider changes the settings of
@@ -435,4 +446,3 @@ spec:
   providerConfigRef:
     name: admin-keys
 ```
-

content/v1.13/concepts/providers.md

@@ -15,6 +15,7 @@ providing
 logic for any external resources.
 
 Examples of providers include:
+
 * [Provider AWS](https://github.com/upbound/provider-aws)
 * [Provider Azure](https://github.com/upbound/provider-azure)
 * [Provider GCP](https://github.com/upbound/provider-gcp)
@@ -169,6 +170,7 @@ install times.
 The Crossplane community has more
 [details on scaling CRDs](https://github.com/crossplane/crossplane/blob/master/design/one-pager-crd-scaling.md).
 {{< /hint >}}
+
 ### Provider conditions
 
 Crossplane uses a standard set of `Conditions` for Providers.  
@@ -193,16 +195,20 @@ Status:
 ```
 
 #### Types
+
 Provider `Conditions` support two `Types`:
+
 * `Type: Installed` - the Provider package installed but isn't ready for use.
 * `Type: Healthy` - The Provider package is ready to use.
 
 #### Reasons
+
 Each `Reason` relates to a specific `Type` and `Status`. Crossplane uses the
 following `Reasons` for Provider `Conditions`.
 
 <!-- vale Google.Headings = NO -->
 ##### InactivePackageRevision
+
 `Reason: InactivePackageRevision` indicates the Provider Package is using an
 inactive Provider Package Revision.
 
@@ -233,6 +239,7 @@ Reason: ActivePackageRevision
 
 <!-- vale Google.Headings = NO -->
 ##### HealthyPackageRevision
+
 The Provider is fully installed and ready to use.
 
 {{<hint "tip" >}}
@@ -267,7 +274,6 @@ Reason: UnhealthyPackageRevision
 ##### UnknownPackageRevisionHealth
 <!-- vale Google.Headings = YES -->
 
-
 The status of the Provider Package Revision is `Unknown`. The Provider Package
 Revision may be installing or has an issue.
 
@@ -285,6 +291,7 @@ Reason: UnknownPackageRevisionHealth
 ## Configure a Provider
 
 Providers have two different types of configurations:
+
 * _Controller configurations_ that change the settings of the Provider pod
   running inside the Kubernetes cluster. For example, Pod `toleration`.
 * _Provider configurations_ that change settings used when communicating with
@@ -297,12 +304,16 @@ Apply `ProviderConfig` objects to managed resources.
 {{< /hint >}}
 
 ### Controller configuration
+
 {{< hint "important" >}}
-The Crossplane community deprecated the `ControllerConfig` type in v1.11.
+The Crossplane community deprecated the `ControllerConfig` type in v1.11 to
+indicate that no further enhancements will be made to it.
 Applying a Controller configuration generates a deprecation warning.
 
 Controller configurations are still supported until there is a replacement type
-in a future Crossplane version.
+in a future Crossplane version. You can read more about the design of
+[Package Runtime Config](https://github.com/crossplane/crossplane/blob/master/design/one-pager-package-runtime-config.md)
+which will replace it in the future.
 {{< /hint >}}
 
 Applying a Crossplane `ControllerConfig` to a Provider changes the settings of
@@ -433,4 +444,3 @@ spec:
   providerConfigRef:
     name: admin-keys
 ```
-