From 0ad18e9f788ffa1e3ceb92f66311d9d5f2c132a4 Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Tue, 5 Aug 2025 16:23:31 -0700 Subject: [PATCH] Fix all links after replacing master with v2.0-preview A lot of our content dirs had links to master when they shouldn't have. These are now replaced with local links. Signed-off-by: Nic Cope --- content/master/_index.md | 2 +- content/master/whats-new/_index.md | 2 +- .../v1.18/concepts/composition-revisions.md | 6 ++--- content/v1.18/concepts/connection-details.md | 24 +++++++++---------- content/v1.18/getting-started/provider-aws.md | 2 +- .../v1.18/getting-started/provider-azure.md | 2 +- content/v1.18/getting-started/provider-gcp.md | 2 +- content/v1.18/guides/multi-tenant.md | 6 ++--- content/v1.18/guides/self-signed-ca-certs.md | 2 +- .../v1.18/guides/troubleshoot-crossplane.md | 4 ++-- .../v1.19/concepts/composition-revisions.md | 6 ++--- content/v1.19/concepts/connection-details.md | 24 +++++++++---------- content/v1.19/getting-started/provider-aws.md | 2 +- .../v1.19/getting-started/provider-azure.md | 2 +- content/v1.19/getting-started/provider-gcp.md | 2 +- content/v1.19/guides/multi-tenant.md | 6 ++--- content/v1.19/guides/self-signed-ca-certs.md | 2 +- .../v1.19/guides/troubleshoot-crossplane.md | 2 +- .../v1.20/concepts/composition-revisions.md | 6 ++--- content/v1.20/concepts/connection-details.md | 24 +++++++++---------- content/v1.20/getting-started/provider-aws.md | 2 +- .../v1.20/getting-started/provider-azure.md | 2 +- content/v1.20/getting-started/provider-gcp.md | 2 +- content/v1.20/guides/multi-tenant.md | 6 ++--- content/v1.20/guides/self-signed-ca-certs.md | 2 +- .../v1.20/guides/troubleshoot-crossplane.md | 4 ++-- content/v2.0-preview/whats-new/_index.md | 2 +- 27 files changed, 74 insertions(+), 74 deletions(-) diff --git a/content/master/_index.md b/content/master/_index.md index 465c3f85..00a6c950 100644 --- a/content/master/_index.md +++ b/content/master/_index.md @@ -12,7 +12,7 @@ for platform engineering. Crossplane organizes its documentation into the following sections: -* [What's Crossplane?]({{}}) introduces Crossplane +* [What's Crossplane?]({{}}) introduces Crossplane and explains why you should use it. * [What's New in v2?]({{}}) highlights what's changed in diff --git a/content/master/whats-new/_index.md b/content/master/whats-new/_index.md index 58e39fc5..8237297f 100644 --- a/content/master/whats-new/_index.md +++ b/content/master/whats-new/_index.md @@ -47,7 +47,7 @@ Read about Crossplane v2's [backward compatibility](#backward-compatibility). {{}} This page assumes you're familiar with Crossplane. New to Crossplane? Read -[What's Crossplane]({{}}) instead. +[What's Crossplane]({{}}) instead. {{}} diff --git a/content/v1.18/concepts/composition-revisions.md b/content/v1.18/concepts/composition-revisions.md index 877c5feb..74c203aa 100644 --- a/content/v1.18/concepts/composition-revisions.md +++ b/content/v1.18/concepts/composition-revisions.md @@ -449,7 +449,7 @@ vpc-staging True myvpcs.aws.example.upbound.io-727b3c8 Automatic map[c {{< /hint >}} -[composition type]: {{}} -[Compositions]: {{}} +[composition type]: {{}} +[Compositions]: {{}} [canary]: https://martinfowler.com/bliki/CanaryRelease.html -[install guide]: {{}} +[install guide]: {{}} diff --git a/content/v1.18/concepts/connection-details.md b/content/v1.18/concepts/connection-details.md index 1de4a607..b65b7956 100644 --- a/content/v1.18/concepts/connection-details.md +++ b/content/v1.18/concepts/connection-details.md @@ -5,14 +5,14 @@ description: "How to create and manage connection details across Crossplane mana --- Using connection details in Crossplane requires the following components: -* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). -* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). +* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). +* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). * Define the `writeConnectionSecretToRef` name and namespace for each resource in the - [Composition]({{}}). + [Composition]({{}}). * Define the list of secret keys produced by each composed resource with in the - [Composition]({{}}). + [Composition]({{}}). * Optionally, define the `connectionSecretKeys` in a - [CompositeResourceDefinition]({{}}). + [CompositeResourceDefinition]({{}}). {{}} This guide discusses creating Kubernetes secrets. @@ -23,7 +23,7 @@ with an external secret store. {{}} ## Background -When a [Provider]({{}}) creates a managed +When a [Provider]({{}}) creates a managed resource, the resource may generate resource-specific details. These details can include usernames, passwords or connection details like an IP address. @@ -37,10 +37,10 @@ detail_ from a managed resource. When a managed resource is part of a -[Composition]({{}}), the Composition, -[Composite Resource Definition]({{}}) +[Composition]({{}}), the Composition, +[Composite Resource Definition]({{}}) and optionally, the -[Claim]({{}}) define what details are visible +[Claim]({{}}) define what details are visible and where they're stored. @@ -213,9 +213,9 @@ spec: When a managed resource creates connection secrets, Crossplane can write the secrets to a -[Kubernetes secret]({{}}) +[Kubernetes secret]({{}}) or an -[external secret store]({{}}). +[external secret store]({{}}). @@ -223,7 +223,7 @@ Creating an individual managed resource shows the connection secrets the resource creates. {{}} -Read the [managed resources]({{}}) +Read the [managed resources]({{}}) documentation for more information on configuring resources and storing connection secrets for individual resources. {{< /hint >}} diff --git a/content/v1.18/getting-started/provider-aws.md b/content/v1.18/getting-started/provider-aws.md index 56a09394..aa50939c 100644 --- a/content/v1.18/getting-started/provider-aws.md +++ b/content/v1.18/getting-started/provider-aws.md @@ -23,7 +23,7 @@ This quickstart requires: * an AWS account with permissions to create an S3 storage bucket * AWS [access keys](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-creds) -{{}} +{{}} ## Install the AWS provider diff --git a/content/v1.18/getting-started/provider-azure.md b/content/v1.18/getting-started/provider-azure.md index e091da5f..7ef4891e 100644 --- a/content/v1.18/getting-started/provider-azure.md +++ b/content/v1.18/getting-started/provider-azure.md @@ -25,7 +25,7 @@ This quickstart requires: [Virtual Network](https://learn.microsoft.com/en-us/azure/virtual-network/) * an Azure account with permissions to create an Azure [service principal](https://learn.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) and an [Azure resource group](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) -{{}} +{{}} ## Install the Azure provider diff --git a/content/v1.18/getting-started/provider-gcp.md b/content/v1.18/getting-started/provider-gcp.md index 5783a5ba..1f7b3b92 100644 --- a/content/v1.18/getting-started/provider-gcp.md +++ b/content/v1.18/getting-started/provider-gcp.md @@ -22,7 +22,7 @@ This quickstart requires: * GCP [account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys) * GCP [Project ID](https://support.google.com/googleapi/answer/7014113?hl=en) -{{}} +{{}} ## Install the GCP provider diff --git a/content/v1.18/guides/multi-tenant.md b/content/v1.18/guides/multi-tenant.md index 1bd4c9d8..4499d3ca 100644 --- a/content/v1.18/guides/multi-tenant.md +++ b/content/v1.18/guides/multi-tenant.md @@ -304,16 +304,16 @@ dedicated control planes to many tenants within a single organization. -[managed resources]: {{}} +[managed resources]: {{}} [RBAC]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ -[Composition]: {{}} +[Composition]: {{}} [CustomResourceDefinitions]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ [Open Policy Agent]: https://www.openpolicyagent.org/ [Rego]: https://www.openpolicyagent.org/docs/latest/policy-language/ [Gatekeeper]: https://open-policy-agent.github.io/gatekeeper/website/docs/ [here]: https://youtu.be/TaF0_syejXc [Multiple Source Field patching]: https://github.com/crossplane/crossplane/pull/2093 -[Configuration packages]: {{}} +[Configuration packages]: {{}} [OCI images]: https://github.com/opencontainers/image-spec [EKS Cluster]: https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/examples/eks/v1beta2/cluster.yaml [provider-aws]: https://github.com/crossplane-contrib/provider-upjet-aws diff --git a/content/v1.18/guides/self-signed-ca-certs.md b/content/v1.18/guides/self-signed-ca-certs.md index b139c687..e95a96c7 100644 --- a/content/v1.18/guides/self-signed-ca-certs.md +++ b/content/v1.18/guides/self-signed-ca-certs.md @@ -11,7 +11,7 @@ registries, it must be configured to trust the CA and Intermediate certs. Crossplane needs to be installed via the Helm chart with the `registryCaBundleConfig.name` and `registryCaBundleConfig.key` parameters -defined. See [Install Crossplane]({{}}). +defined. See [Install Crossplane]({{}}). ## Configure diff --git a/content/v1.18/guides/troubleshoot-crossplane.md b/content/v1.18/guides/troubleshoot-crossplane.md index c396878e..cce15da1 100644 --- a/content/v1.18/guides/troubleshoot-crossplane.md +++ b/content/v1.18/guides/troubleshoot-crossplane.md @@ -241,7 +241,7 @@ Debugging Composite Resource Definition (XRD) is like debugging Compositions. You can use install providers in two ways: `configuration.pkg.crossplane.io` and `provider.pkg.crossplane.io`. You can use either one to install providers with no functional differences to providers themselves. If you define a `configuration.pkg.crossplane.io` object, Crossplane creates a -`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) +`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) for more information about Crossplane Packages. If you are experiencing provider issues, steps below are a good starting point. @@ -451,7 +451,7 @@ To follow the references: [Pausing Providers]: #pausing-providers [Deleting When a Resource Hangs]: #deleting-when-a-resource-hangs [Installing Crossplane Package]: #installing-crossplane-package -[Crossplane package]: /master/concepts/packages/ +[Crossplane package]: ../concepts/packages/ [Handling Crossplane Package Dependency]: #handling-crossplane-package-dependency [semver spec]: https://github.com/Masterminds/semver#basic-comparisons diff --git a/content/v1.19/concepts/composition-revisions.md b/content/v1.19/concepts/composition-revisions.md index 877c5feb..74c203aa 100644 --- a/content/v1.19/concepts/composition-revisions.md +++ b/content/v1.19/concepts/composition-revisions.md @@ -449,7 +449,7 @@ vpc-staging True myvpcs.aws.example.upbound.io-727b3c8 Automatic map[c {{< /hint >}} -[composition type]: {{}} -[Compositions]: {{}} +[composition type]: {{}} +[Compositions]: {{}} [canary]: https://martinfowler.com/bliki/CanaryRelease.html -[install guide]: {{}} +[install guide]: {{}} diff --git a/content/v1.19/concepts/connection-details.md b/content/v1.19/concepts/connection-details.md index 1de4a607..b65b7956 100644 --- a/content/v1.19/concepts/connection-details.md +++ b/content/v1.19/concepts/connection-details.md @@ -5,14 +5,14 @@ description: "How to create and manage connection details across Crossplane mana --- Using connection details in Crossplane requires the following components: -* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). -* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). +* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). +* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). * Define the `writeConnectionSecretToRef` name and namespace for each resource in the - [Composition]({{}}). + [Composition]({{}}). * Define the list of secret keys produced by each composed resource with in the - [Composition]({{}}). + [Composition]({{}}). * Optionally, define the `connectionSecretKeys` in a - [CompositeResourceDefinition]({{}}). + [CompositeResourceDefinition]({{}}). {{}} This guide discusses creating Kubernetes secrets. @@ -23,7 +23,7 @@ with an external secret store. {{}} ## Background -When a [Provider]({{}}) creates a managed +When a [Provider]({{}}) creates a managed resource, the resource may generate resource-specific details. These details can include usernames, passwords or connection details like an IP address. @@ -37,10 +37,10 @@ detail_ from a managed resource. When a managed resource is part of a -[Composition]({{}}), the Composition, -[Composite Resource Definition]({{}}) +[Composition]({{}}), the Composition, +[Composite Resource Definition]({{}}) and optionally, the -[Claim]({{}}) define what details are visible +[Claim]({{}}) define what details are visible and where they're stored. @@ -213,9 +213,9 @@ spec: When a managed resource creates connection secrets, Crossplane can write the secrets to a -[Kubernetes secret]({{}}) +[Kubernetes secret]({{}}) or an -[external secret store]({{}}). +[external secret store]({{}}). @@ -223,7 +223,7 @@ Creating an individual managed resource shows the connection secrets the resource creates. {{}} -Read the [managed resources]({{}}) +Read the [managed resources]({{}}) documentation for more information on configuring resources and storing connection secrets for individual resources. {{< /hint >}} diff --git a/content/v1.19/getting-started/provider-aws.md b/content/v1.19/getting-started/provider-aws.md index 56a09394..1548be21 100644 --- a/content/v1.19/getting-started/provider-aws.md +++ b/content/v1.19/getting-started/provider-aws.md @@ -23,7 +23,7 @@ This quickstart requires: * an AWS account with permissions to create an S3 storage bucket * AWS [access keys](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-creds) -{{}} +{{}} ## Install the AWS provider diff --git a/content/v1.19/getting-started/provider-azure.md b/content/v1.19/getting-started/provider-azure.md index e091da5f..8823ef8f 100644 --- a/content/v1.19/getting-started/provider-azure.md +++ b/content/v1.19/getting-started/provider-azure.md @@ -25,7 +25,7 @@ This quickstart requires: [Virtual Network](https://learn.microsoft.com/en-us/azure/virtual-network/) * an Azure account with permissions to create an Azure [service principal](https://learn.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) and an [Azure resource group](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) -{{}} +{{}} ## Install the Azure provider diff --git a/content/v1.19/getting-started/provider-gcp.md b/content/v1.19/getting-started/provider-gcp.md index 5783a5ba..8558273d 100644 --- a/content/v1.19/getting-started/provider-gcp.md +++ b/content/v1.19/getting-started/provider-gcp.md @@ -22,7 +22,7 @@ This quickstart requires: * GCP [account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys) * GCP [Project ID](https://support.google.com/googleapi/answer/7014113?hl=en) -{{}} +{{}} ## Install the GCP provider diff --git a/content/v1.19/guides/multi-tenant.md b/content/v1.19/guides/multi-tenant.md index 1bd4c9d8..4499d3ca 100644 --- a/content/v1.19/guides/multi-tenant.md +++ b/content/v1.19/guides/multi-tenant.md @@ -304,16 +304,16 @@ dedicated control planes to many tenants within a single organization. -[managed resources]: {{}} +[managed resources]: {{}} [RBAC]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ -[Composition]: {{}} +[Composition]: {{}} [CustomResourceDefinitions]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ [Open Policy Agent]: https://www.openpolicyagent.org/ [Rego]: https://www.openpolicyagent.org/docs/latest/policy-language/ [Gatekeeper]: https://open-policy-agent.github.io/gatekeeper/website/docs/ [here]: https://youtu.be/TaF0_syejXc [Multiple Source Field patching]: https://github.com/crossplane/crossplane/pull/2093 -[Configuration packages]: {{}} +[Configuration packages]: {{}} [OCI images]: https://github.com/opencontainers/image-spec [EKS Cluster]: https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/examples/eks/v1beta2/cluster.yaml [provider-aws]: https://github.com/crossplane-contrib/provider-upjet-aws diff --git a/content/v1.19/guides/self-signed-ca-certs.md b/content/v1.19/guides/self-signed-ca-certs.md index b139c687..e95a96c7 100644 --- a/content/v1.19/guides/self-signed-ca-certs.md +++ b/content/v1.19/guides/self-signed-ca-certs.md @@ -11,7 +11,7 @@ registries, it must be configured to trust the CA and Intermediate certs. Crossplane needs to be installed via the Helm chart with the `registryCaBundleConfig.name` and `registryCaBundleConfig.key` parameters -defined. See [Install Crossplane]({{}}). +defined. See [Install Crossplane]({{}}). ## Configure diff --git a/content/v1.19/guides/troubleshoot-crossplane.md b/content/v1.19/guides/troubleshoot-crossplane.md index c396878e..85038381 100644 --- a/content/v1.19/guides/troubleshoot-crossplane.md +++ b/content/v1.19/guides/troubleshoot-crossplane.md @@ -241,7 +241,7 @@ Debugging Composite Resource Definition (XRD) is like debugging Compositions. You can use install providers in two ways: `configuration.pkg.crossplane.io` and `provider.pkg.crossplane.io`. You can use either one to install providers with no functional differences to providers themselves. If you define a `configuration.pkg.crossplane.io` object, Crossplane creates a -`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) +`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) for more information about Crossplane Packages. If you are experiencing provider issues, steps below are a good starting point. diff --git a/content/v1.20/concepts/composition-revisions.md b/content/v1.20/concepts/composition-revisions.md index 877c5feb..74c203aa 100644 --- a/content/v1.20/concepts/composition-revisions.md +++ b/content/v1.20/concepts/composition-revisions.md @@ -449,7 +449,7 @@ vpc-staging True myvpcs.aws.example.upbound.io-727b3c8 Automatic map[c {{< /hint >}} -[composition type]: {{}} -[Compositions]: {{}} +[composition type]: {{}} +[Compositions]: {{}} [canary]: https://martinfowler.com/bliki/CanaryRelease.html -[install guide]: {{}} +[install guide]: {{}} diff --git a/content/v1.20/concepts/connection-details.md b/content/v1.20/concepts/connection-details.md index 1de4a607..b65b7956 100644 --- a/content/v1.20/concepts/connection-details.md +++ b/content/v1.20/concepts/connection-details.md @@ -5,14 +5,14 @@ description: "How to create and manage connection details across Crossplane mana --- Using connection details in Crossplane requires the following components: -* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). -* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). +* Defining the `writeConnectionSecretToRef.name` in a [Claim]({{}}). +* Defining the `writeConnectionSecretsToNamespace` value in the [Composition]({{}}). * Define the `writeConnectionSecretToRef` name and namespace for each resource in the - [Composition]({{}}). + [Composition]({{}}). * Define the list of secret keys produced by each composed resource with in the - [Composition]({{}}). + [Composition]({{}}). * Optionally, define the `connectionSecretKeys` in a - [CompositeResourceDefinition]({{}}). + [CompositeResourceDefinition]({{}}). {{}} This guide discusses creating Kubernetes secrets. @@ -23,7 +23,7 @@ with an external secret store. {{}} ## Background -When a [Provider]({{}}) creates a managed +When a [Provider]({{}}) creates a managed resource, the resource may generate resource-specific details. These details can include usernames, passwords or connection details like an IP address. @@ -37,10 +37,10 @@ detail_ from a managed resource. When a managed resource is part of a -[Composition]({{}}), the Composition, -[Composite Resource Definition]({{}}) +[Composition]({{}}), the Composition, +[Composite Resource Definition]({{}}) and optionally, the -[Claim]({{}}) define what details are visible +[Claim]({{}}) define what details are visible and where they're stored. @@ -213,9 +213,9 @@ spec: When a managed resource creates connection secrets, Crossplane can write the secrets to a -[Kubernetes secret]({{}}) +[Kubernetes secret]({{}}) or an -[external secret store]({{}}). +[external secret store]({{}}). @@ -223,7 +223,7 @@ Creating an individual managed resource shows the connection secrets the resource creates. {{}} -Read the [managed resources]({{}}) +Read the [managed resources]({{}}) documentation for more information on configuring resources and storing connection secrets for individual resources. {{< /hint >}} diff --git a/content/v1.20/getting-started/provider-aws.md b/content/v1.20/getting-started/provider-aws.md index 56a09394..21cdb829 100644 --- a/content/v1.20/getting-started/provider-aws.md +++ b/content/v1.20/getting-started/provider-aws.md @@ -23,7 +23,7 @@ This quickstart requires: * an AWS account with permissions to create an S3 storage bucket * AWS [access keys](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-creds) -{{}} +{{}} ## Install the AWS provider diff --git a/content/v1.20/getting-started/provider-azure.md b/content/v1.20/getting-started/provider-azure.md index e091da5f..5672cefc 100644 --- a/content/v1.20/getting-started/provider-azure.md +++ b/content/v1.20/getting-started/provider-azure.md @@ -25,7 +25,7 @@ This quickstart requires: [Virtual Network](https://learn.microsoft.com/en-us/azure/virtual-network/) * an Azure account with permissions to create an Azure [service principal](https://learn.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) and an [Azure resource group](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal) -{{}} +{{}} ## Install the Azure provider diff --git a/content/v1.20/getting-started/provider-gcp.md b/content/v1.20/getting-started/provider-gcp.md index 5783a5ba..df0d2be2 100644 --- a/content/v1.20/getting-started/provider-gcp.md +++ b/content/v1.20/getting-started/provider-gcp.md @@ -22,7 +22,7 @@ This quickstart requires: * GCP [account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys) * GCP [Project ID](https://support.google.com/googleapi/answer/7014113?hl=en) -{{}} +{{}} ## Install the GCP provider diff --git a/content/v1.20/guides/multi-tenant.md b/content/v1.20/guides/multi-tenant.md index 1bd4c9d8..4499d3ca 100644 --- a/content/v1.20/guides/multi-tenant.md +++ b/content/v1.20/guides/multi-tenant.md @@ -304,16 +304,16 @@ dedicated control planes to many tenants within a single organization. -[managed resources]: {{}} +[managed resources]: {{}} [RBAC]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ -[Composition]: {{}} +[Composition]: {{}} [CustomResourceDefinitions]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ [Open Policy Agent]: https://www.openpolicyagent.org/ [Rego]: https://www.openpolicyagent.org/docs/latest/policy-language/ [Gatekeeper]: https://open-policy-agent.github.io/gatekeeper/website/docs/ [here]: https://youtu.be/TaF0_syejXc [Multiple Source Field patching]: https://github.com/crossplane/crossplane/pull/2093 -[Configuration packages]: {{}} +[Configuration packages]: {{}} [OCI images]: https://github.com/opencontainers/image-spec [EKS Cluster]: https://github.com/crossplane-contrib/provider-upjet-aws/blob/main/examples/eks/v1beta2/cluster.yaml [provider-aws]: https://github.com/crossplane-contrib/provider-upjet-aws diff --git a/content/v1.20/guides/self-signed-ca-certs.md b/content/v1.20/guides/self-signed-ca-certs.md index b139c687..e95a96c7 100644 --- a/content/v1.20/guides/self-signed-ca-certs.md +++ b/content/v1.20/guides/self-signed-ca-certs.md @@ -11,7 +11,7 @@ registries, it must be configured to trust the CA and Intermediate certs. Crossplane needs to be installed via the Helm chart with the `registryCaBundleConfig.name` and `registryCaBundleConfig.key` parameters -defined. See [Install Crossplane]({{}}). +defined. See [Install Crossplane]({{}}). ## Configure diff --git a/content/v1.20/guides/troubleshoot-crossplane.md b/content/v1.20/guides/troubleshoot-crossplane.md index edd16bcb..b043289e 100644 --- a/content/v1.20/guides/troubleshoot-crossplane.md +++ b/content/v1.20/guides/troubleshoot-crossplane.md @@ -240,7 +240,7 @@ Debugging Composite Resource Definition (XRD) is like debugging Compositions. You can use install providers in two ways: `configuration.pkg.crossplane.io` and `provider.pkg.crossplane.io`. You can use either one to install providers with no functional differences to providers themselves. If you define a `configuration.pkg.crossplane.io` object, Crossplane creates a -`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) +`provider.pkg.crossplane.io` object and manages it. Refer to [the Packages documentation]({{}}) for more information about Crossplane Packages. If you are experiencing provider issues, steps below are a good starting point. @@ -450,7 +450,7 @@ To follow the references: [Pausing Providers]: #pausing-providers [Deleting When a Resource Hangs]: #deleting-when-a-resource-hangs [Installing Crossplane Package]: #installing-crossplane-package -[Crossplane package]: /master/concepts/packages/ +[Crossplane package]: ../concepts/packages/ [Handling Crossplane Package Dependency]: #handling-crossplane-package-dependency [semver spec]: https://github.com/Masterminds/semver#basic-comparisons diff --git a/content/v2.0-preview/whats-new/_index.md b/content/v2.0-preview/whats-new/_index.md index 58e39fc5..8237297f 100644 --- a/content/v2.0-preview/whats-new/_index.md +++ b/content/v2.0-preview/whats-new/_index.md @@ -47,7 +47,7 @@ Read about Crossplane v2's [backward compatibility](#backward-compatibility). {{}} This page assumes you're familiar with Crossplane. New to Crossplane? Read -[What's Crossplane]({{}}) instead. +[What's Crossplane]({{}}) instead. {{}}