Reconcile Kubernetes class type objects in a dedicated stage #720
+49
−17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
stefanprodan
added
the
area/server-side-apply
hiddeco
approved these changes
Sep 2, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This PR adds a new stage to the server-side apply where the controller reconciles the Kubernetes Class types (RuntimeClass, PriorityClass, StorageClass, VolumeSnapshotClass, IngressClass, GatewayClass, ClusterClass, etc) after CRDs, but before any other resource type. This allows users to bundle Class types with their consumers, e.g. ClusterClass and Cluster, or IngressClass and Ingress.
Fix: #719
PS. This PR also fixes a flaky test.