Apply CRDs directly without the applier manager #6739
Draft
+135
−146
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.
Description
There's no need to write them to the filesystem. Moreover, we can be sure that whenever the CRD component is initialized, the CRDs have been applied successfully, so we don't need to wait for the applier manager to pick things up.
Add the etcd member reconciler as a cluster component, just as its CRD stack. This ensures that the CRDs get applied before the reconciler is started.
Move unstructured stack application into public function The system RBAC component fed an io.Reader into a resource builder to extract unstructured objects and apply them as a stack in a retry loop. This is a pattern that is reusable across components: Move this into its own function in the applier package.
Type of change
How Has This Been Tested?
Checklist