From c94c5cb9941783ac5057f4845fd06f80b8bafe36 Mon Sep 17 00:00:00 2001 From: richardrobertreitz Date: Wed, 18 Dec 2024 14:27:34 +0000 Subject: [PATCH] Update docs/userguide/crossplane.md --- docs/userguide/crossplane.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide/crossplane.md b/docs/userguide/crossplane.md index b6a6a17..1328a65 100644 --- a/docs/userguide/crossplane.md +++ b/docs/userguide/crossplane.md @@ -25,7 +25,7 @@ The edpbuilder is using Crossplane in several different ways: To bootstrap the edpbuilder a script performs an Crossplane installation including all neccessary Crossplane providers, functions and compositions into a management Kubernetes cluster. The Crossplane edpbuilder composition is then executed and performs the one shot provisioning of the edpbuilder's core applications in, by default, the managemnt cluster. Optionally a new cluster, as a edpbuilder installation destination, can be provisioned as part of the edpbuilder composition. This allows for declarative platform orchestration of IDP's. -After the edpbuilder's core applications have been deployed, [ArgoCD](argocd.md) takes over and deploys all other applications of the edpbuilders stack. +After the edpbuilder's core applications have been deployed, [ArgoCD](argocd.md) takes over and deploys all other applications of the edpbuilder's stack. ---