From f6a69a54caec86d2cc0d30485e417c80039c21ff Mon Sep 17 00:00:00 2001 From: Crossplane Date: Tue, 16 Mar 2021 17:43:05 +0000 Subject: [PATCH] docs snapshot for crossplane version `v1.1` --- docs/v1.1/concepts/managed-resources.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/v1.1/concepts/managed-resources.md b/docs/v1.1/concepts/managed-resources.md index adb3c725..8b7f0232 100644 --- a/docs/v1.1/concepts/managed-resources.md +++ b/docs/v1.1/concepts/managed-resources.md @@ -42,7 +42,7 @@ spec: namespace: crossplane-system providerConfigRef: name: default - reclaimPolicy: Delete + deletionPolicy: Delete ``` In Kubernetes, `spec` top field represents the desired state of the user. @@ -118,7 +118,7 @@ of an `RDSInstance`. Some infrastructure tools such as Terraform delete and recreate the resource to accommodate those changes but Crossplane does not take that route. Unless the -managed resource is deleted and its `reclaimPolicy` is `Delete`, its controller +managed resource is deleted and its `deletionPolicy` is `Delete`, its controller never deletes the external resource in the provider. > Immutable fields are marked as `immutable` in Crossplane codebase but