crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

clean up links 

Signed-off-by: Scott Nichols <n3wscott@upbound.io>
This commit is contained in:
Scott Nichols 2025-08-08 15:20:17 -07:00
parent f05078cc49
commit b22239c8a4
2 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/master/guides/implementing-safestart.md
View File

@ -33,7 +33,7 @@ safe-start transforms how your provider handles resource installation:
Before implementing safe-start, ensure you have:
* Provider built with `crossplane-runtime` v2.0+
* Understanding of [MRDs and activation policies]({{< ref "mrd-activation-policies" >}})
* Understanding of [MRDs and activation policies]({{< ref "using-mrds-and-activation-policies" >}})
* Test environment with Crossplane v2.0+
* CI/CD pipeline that can build and test provider changes

12
content/master/guides/using-mrds-and-activation-policies.md
View File

@ -25,7 +25,7 @@ By the end of this guide, you understand how to:
This guide requires:
* A Kubernetes cluster with at least 2 GB of RAM
* Crossplane v2.0+ [installed on the cluster]({{< ref "install" >}})
* Crossplane v2.0+ [installed on the cluster]({{< ref "../get-started/install" >}})
* `kubectl` configured to access your cluster
## Understand the default activation policy
@ -79,11 +79,6 @@ This approach lets you use Helm chart values to control the default policy.
{{< /tab >}}
{{< /tabs >}}
{{< hint "tip" >}}
Learn more about configuring default activation policies during installation
and best practices in the [MRD activation policies guide]({{< ref "../guides/mrd-activation-policies#default-activation-policy" >}}).
{{< /hint >}}
## Install a provider with safe-start capability
Now install a provider that supports safe-start. This provider creates MRDs
@ -95,7 +90,7 @@ kind: Provider
metadata:
name: provider-aws
spec:
package: xpkg.upbound.io/crossplane-contrib/provider-aws:v0.45.0
package: xpkg.crossplane.io/crossplane-contrib/provider-aws:v2.0.0
```
Apply this configuration:
@ -107,7 +102,7 @@ kind: Provider
metadata:
name: provider-aws
spec:
package: xpkg.upbound.io/crossplane-contrib/provider-aws:v0.45.0
package: xpkg.crossplane.io/crossplane-contrib/provider-aws:v2.0.0
EOF
```
@ -524,6 +519,5 @@ Now that you understand MRDs and activation policies, you can:
* **Plan provider adoption** using safe-start-capable providers
Learn more about:
* [MRD activation policies best practices]({{< ref "../guides/mrd-activation-policies" >}}) - Comprehensive guide including default policy configuration
* [Managed Resource Definitions concepts]({{< ref "managed-resource-definitions" >}})
* [Provider capabilities and safe-start]({{< ref "../packages/provider-capabilities" >}})