From 5707a95bf14d750edc105e2760c6bd6256729e42 Mon Sep 17 00:00:00 2001 From: Luis Rascao Date: Fri, 30 Apr 2021 09:47:27 +0100 Subject: [PATCH] Link provider examples Signed-off-by: Luis Rascao --- docs/concepts/composition.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/concepts/composition.md b/docs/concepts/composition.md index 7b6e1cdcd2f..abe6e562b7a 100644 --- a/docs/concepts/composition.md +++ b/docs/concepts/composition.md @@ -17,8 +17,10 @@ possible, but they’re also opinionated. Common functionality like status conditions and references work the same no matter which provider you're using - all managed resources comply with the Crossplane Resource Model, or XRM. Despite the name, 'provider' doesn’t necessarily mean 'cloud provider'. The Crossplane -community has built providers that add support for managing databases on a SQL -server, managing Helm releases, and ordering pizza. +community has built providers that add support for managing databases on a [SQL +server](https://github.com/crossplane-contrib/provider-sql), managing +[Helm releases](https://github.com/crossplane-contrib/provider-helm/), +and [ordering pizza](https://blog.crossplane.io/providers-101-ordering-pizza-with-kubernetes-and-crossplane/). Composition allows platform builders to define new custom resources that are composed of managed resources. We call these composite resources, or XRs. An XR