📖 Update note on runtime SDK that in-place updates work for non CC clusters #13283
+1
−2
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 pull request clarifies the documentation for the Runtime SDK feature by specifying that only certain hooks require the ClusterClass feature to be enabled. It also notes that In-Place Update Hooks are an exception to this requirement.
Documentation clarification:
index.mdto state that all currently implemented hooks, except for In-Place Update Hooks, require the ClusterClass feature and are only invoked for Clusters created using ClusterClass.Reference conversation on slack
/area runtime-sdk