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

Don't say "think", restructure important note about dupes 

Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2024-01-31 12:45:29 -08:00
parent c50047e716
commit 0aef9a688b
1 changed files with 14 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
content/master/concepts/managed-resources.md
View File

@ -672,9 +672,9 @@ A provider uses the
{{<hover label="creation" line="7">}}crossplane.io/external-name{{</hover>}} {{<hover label="creation" line="7">}}crossplane.io/external-name{{</hover>}}
annotation to lookup a managed resource in an external system. annotation to lookup a managed resource in an external system.
If the provider can't find a managed resource in an external system, it thinks The provider looks up the resource in the external system to determine if it
the resource doesn't exist. When the provider thinks a resource doesn't exist exists, and if it matches the managed resource's desired state. If the provider
it creates the resource. can't find the resource, it creates it.
Some external systems don't let a provider specify a resource's name when the Some external systems don't let a provider specify a resource's name when the
provider creates it. Instead the external system generates an nondeterministic provider creates it. Instead the external system generates an nondeterministic
@ -688,15 +688,21 @@ A provider can't guarantee that it can save the annotation. The provider could
restart or lose network connectivity between creating the resource and saving restart or lose network connectivity between creating the resource and saving
the annotation. the annotation.
{{<hint "important">}}
Anytime an external system generates a resource's name there is a risk the
provider could leak the resource.
{{</hint>}}
A provider can detect that it might have leaked a resource. If the provider A provider can detect that it might have leaked a resource. If the provider
thinks it might have leaked a resource, it stops reconciling it until you tell thinks it might have leaked a resource, it stops reconciling it until you tell
the provider it's safe to proceed. the provider it's safe to proceed.
{{<hint "important">}}
Anytime an external system generates a resource's name there is a risk the
provider could leak the resource.
The safest thing for a provider to do when it detects that it might have leaked
a resource is to stop and wait for human intervention.
This ensures the provider doesn't create duplicates of the leaked resource.
Duplicate resources can be costly and dangerous.
{{</hint>}}
When a provider thinks it might have leaked a resource it creates a `cannot When a provider thinks it might have leaked a resource it creates a `cannot
determine creation result` event associated with the managed resource. Use determine creation result` event associated with the managed resource. Use
`kubectl describe` to see the event. `kubectl describe` to see the event.
@ -731,14 +737,6 @@ resource's annotations at the same time. If the provider couldn't update the
creation annotations after it created the resource, it also couldn't update the creation annotations after it created the resource, it also couldn't update the
`crossplane.io/external-name` annotation. `crossplane.io/external-name` annotation.
{{<hint "important">}}
The safest thing for a provider to do when it detects that it might have leaked
a resource is to stop and wait for human intervention.
This ensures the provider doesn't create duplicates of the leaked resource.
Duplicate resources can be costly and dangerous.
{{</hint>}}
{{<hint "tip">}} {{<hint "tip">}}
If a resource has a `cannot determine creation result` error, inspect the If a resource has a `cannot determine creation result` error, inspect the
external system. external system.