mirror of https://github.com/crossplane/docs.git
docs snapshot for crossplane version `v1.1`
This commit is contained in:
parent
3f1fdb23a0
commit
f6a69a54ca
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue