Update documentation regarding node deletion changes #1067
+6
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR updates documentation to account for changes made by #1055 , regarding the
node.machine.sapcloud.io/trigger-deletion-by-mcmannotation.docs/faq.mdto clarify that deleting a node now immediately triggers the deletion and replacement of the corresponding machine, and that thetrigger-deletion-by-mcmannotation is no longer supported on node objects but is still supported on machine and machineDeployment objects for CA-MCM integration.TriggerDeletionByMCMinpkg/util/provider/machineutils/utils.goRelease note: