Remove reference to importing resources

This page was deleted (for now).

Signed-off-by: Nic Cope <[email protected]>

Author: negz

content/v2.0-preview/concepts/compositions.md

@@ -310,15 +310,6 @@ When resources inside a Composition create connection details Crossplane creates
 a Kubernetes secret object for each managed resource generating connection
 details.
 
-{{<hint "note">}}
-This section discusses creating Kubernetes secrets.
-Crossplane also supports using external secret stores like
-[HashiCorp Vault](https://www.vaultproject.io/).
-
-Read the [external secrets store guide]({{<ref "../guides/vault-as-secret-store">}}) for more information on using Crossplane
-with an external secret store.
-{{</hint >}}
-
 #### Composed resource secrets
 
 Inside the `spec` of each resource producing connection details, define the
@@ -366,49 +357,6 @@ key1   connection.crossplane.io/v1alpha1   4      4m30s
 Remember to create a unique name for each secret.
 {{< /hint >}}
 
-#### External secret stores
-
-Crossplane
-[External Secret Stores]({{<ref "../guides/vault-as-secret-store" >}})
-write secrets and connection details to external secret stores like HashiCorp
-Vault.
-
-{{<hint "important" >}}
-External Secret Stores are an alpha feature.
-
-They're not recommended for production use. Crossplane disables External Secret
-Stores by default.
-{{< /hint >}}
-
-Use `publishConnectionDetailsWithStoreConfigRef` in place of
-`writeConnectionSecretsToNamespace` to define the `StoreConfig` to save
-connection details to.
-
-For example, using a `StoreConfig` with the `name` "vault," use
-`publishConnectionDetailsWithStoreConfigRef.name` matching the
-`StoreConfig.name`, in this example, "vault."
-
-
-```yaml {label="gcp-storeconfig",copy-lines="none"}
-apiVersion: gcp.crossplane.io/v1alpha1
-kind: StoreConfig
-metadata:
-  name: vault
-# Removed for brevity.
----
-apiVersion: apiextensions.crossplane.io/v1
-kind: Composition
-# Removed for Brevity
-spec:
-  publishConnectionDetailsWithStoreConfigRef:
-    name: vault
-  # Removed for brevity
-```
-
-For more details read the
-[External Secret Stores]({{<ref "../guides/vault-as-secret-store" >}})
-integration guide.
-
 ## Test a composition
 
 You can preview the output of any composition using the Crossplane CLI. You

content/v2.0-preview/concepts/managed-resources.md

@@ -438,7 +438,7 @@ Crossplane supports the following policies:
 | `Create` | If the external resource doesn't exist, Crossplane creates it based on the managed resource settings. |
 | `Delete` | Crossplane can delete the external resource when deleting the managed resource. |
 | `LateInitialize` | Crossplane initializes some external resource settings not defined in the `spec.forProvider` of the managed resource. See [the late initialization]({{<ref "./managed-resources#late-initialization" >}}) section for more details. |
-| `Observe` | Crossplane only observes the resource and doesn't make any changes. Used for [observe only resources]({{<ref "../guides/import-existing-resources#import-resources-automatically">}}). |
+| `Observe` | Crossplane only observes the resource and doesn't make any changes. Used for observe only resources. |
 | `Update` | Crossplane changes the external resource when changing the managed resource. |
 {{</table >}}
 
@@ -454,7 +454,7 @@ The following is a list of common policy combinations:
 | {{<check>}}      |        | {{<check>}}              | {{<check>}}       |        | Crossplane doesn't delete the external resource when deleting the managed resource. Crossplane doesn't apply changes to the external resource after creation. |
 | {{<check>}}      |        |                | {{<check>}}       | {{<check>}}      | Crossplane doesn't delete the external resource when deleting the managed resource. Crossplane doesn't import any settings from the external resource. |
 | {{<check>}}      |        |                | {{<check>}}       |        | Crossplane creates the external resource but doesn't apply any changes to the external resource or managed resource. Crossplane can't delete the resource. |
-|        |        |                | {{<check>}}       |        | Crossplane only observes a resource. Used for [observe only resources]({{<ref "../guides/import-existing-resources#import-resources-automatically">}}). |
+|        |        |                | {{<check>}}       |        | Crossplane only observes a resource. |
 |        |        |                |         |        | No policy set. An alternative method for [pausing](#paused) a resource.                                                                                              |
 {{< /table >}}
 
@@ -615,43 +615,6 @@ spec:
         annotation-tag: annotation-value
 ```
 
-#### Publish secrets to an external secrets store
-
-Publishing secrets data to an external secret store like 
-[HashiCorp Vault](https://www.vaultproject.io/) relies on a 
-{{<hover label="configref" line="8">}}publishConnectionDetailsTo.configRef{{</hover>}}. 
-
-The 
-{{<hover label="configref" line="9">}}configRef.name{{</hover>}} references a 
-{{<hover label="storeconfig" line="4">}}StoreConfig{{</hover>}}
-object. 
-
-```yaml {label="configref",copy-lines="none"}
-apiVersion: rds.aws.upbound.io/v1beta1
-kind: Instance
-spec:
-  forProvider:
-  # Removed for brevity
-  publishConnectionDetailsTo:
-    name: rds-kubernetes-secret
-    configRef: 
-      name: my-vault-storeconfig
-```
-
-```yaml {label="storeconfig",copy-lines="none"}
-apiVersion: secrets.crossplane.io/v1alpha1
-kind: StoreConfig
-metadata:
-  name: my-vault-storeconfig
-# Removed for brevity
-```
-
-{{<hint "tip" >}}
-Read the 
-[Vault as an External Secrets Store]({{<ref "../guides/vault-as-secret-store">}})
-guide for details on using StoreConfig objects.
-{{< /hint >}}
-
 ## Annotations
 
 Crossplane applies a standard set of Kubernetes `annotations` to managed

content/v2.0-preview/concepts/providers.md

@@ -618,45 +618,13 @@ Reason: UnknownPackageRevisionHealth
 
 Providers have two different types of configurations:
 
-* _Controller configurations_ that change the settings of the Provider pod
+* _Runtime configurations_ that change the settings of the Provider pod
   running inside the Kubernetes cluster. For example, setting a `toleration` on
   the Provider pod.
 
 * _Provider configurations_ that change settings used when communicating with
   an external provider. For example, cloud provider authentication.
 
-{{<hint "important" >}}
-Apply `ControllerConfig` objects to Providers.  
-
-Apply `ProviderConfig` objects to managed resources.
-{{< /hint >}}
-
-### Controller configuration
-
-{{< hint "important" >}}
-<!-- vale write-good.Passive = NO -->
-<!-- vale gitlab.FutureTense = NO -->
-The `ControllerConfig` type was deprecated in v1.11 and will be removed in
-a future release.
-<!-- vale write-good.Passive = YES -->
-<!-- vale gitlab.FutureTense = YES -->
-
-[`DeploymentRuntimeConfig`]({{<ref "#runtime-configuration" >}}) is the
-replacement for Controller configuration and is available in v1.14+.
-{{< /hint >}}
-
-Applying a Crossplane `ControllerConfig` to a Provider changes the settings of
-the Provider's pod. The
-[Crossplane ControllerConfig schema]({{< ref "../api#ControllerConfig-spec" >}})
-defines the supported set of ControllerConfig settings.
-
-The most common use case for ControllerConfigs are providing `args` to a
-Provider's pod enabling optional services. For example, enabling
-[external secret stores]({{< ref "../guides/vault-as-secret-store#enable-external-secret-stores-in-the-provider" >}})
-for a Provider.
-
-Each Provider determines their supported set of `args`.
-
 ### Runtime configuration
 
 {{<hint "important" >}}
@@ -667,22 +635,14 @@ It's on by default, and you can disable it by passing
 {{< /hint >}}
 
 Runtime configuration is a generalized mechanism for configuring the runtime for
-Crossplane packages with a runtime, namely `Providers` and `Functions`. It
-replaces the deprecated `ControllerConfig` type and is available in v1.14+.
+Crossplane packages with a runtime, namely `Providers` and `Functions`.
 
 With its default configuration, Crossplane uses Kubernetes Deployments to
 deploy runtime for packages, more specifically, a controller for a `Provider`
 or a gRPC server for a `Function`. It's possible to configure the runtime
 manifest by applying a `DeploymentRuntimeConfig` and referencing it in the
 `Provider` or `Function` object.
 
-{{<hint "note" >}}
-Different from `ControllerConfig`, `DeploymentRuntimeConfig` embed the whole
-Kubernetes Deployment spec, which allows for more flexibility in configuring
-the runtime. Refer to the [design document](https://github.com/crossplane/crossplane/blob/2c5e7f07ba9e3d83d1c85169bbde685de8514ab8/design/one-pager-package-runtime-config.md)
-for more details.
-{{< /hint >}}
-
 As an example, to enable the external secret stores alpha feature for a `Provider`
 by adding the `--enable-external-secret-stores` argument to the controller,
 one can apply the following:

content/v2.0-preview/guides/crossplane-with-argo-cd.md

@@ -133,7 +133,6 @@ data:
           "Composition",
           "CompositionRevision",
           "DeploymentRuntimeConfig",
-          "ControllerConfig",
           "ProviderConfig",
           "ProviderConfigUsage"
         }