-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make ordering configurable #4019
Make ordering configurable #4019
Commits on Dec 2, 2022
-
api: Add new types for customizeable resource ordering
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
Configuration menu - View commit details
-
Copy full SHA for 76ee60d - Browse repository at this point
Copy the full SHA 76ee60dView commit details -
plugins: Implement SortOrderTransformer plugin
Implement the SortOrderTransformer plugin. This plugin allows the user to customize the order that kustomize will output resources in. The API for the plugin is the following: sortOptions: order: legacy | fifo legacySortOptions: orderFirst: - {GVK} orderLast: - {GVK} Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
Configuration menu - View commit details
-
Copy full SHA for 1b2fd3c - Browse repository at this point
Copy the full SHA 1b2fd3cView commit details -
plugins: Add boilerplate and generate code for new SortOrderTransformer
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
Configuration menu - View commit details
-
Copy full SHA for 8e0fc12 - Browse repository at this point
Copy the full SHA 8e0fc12View commit details -
build: Add option to denote if the reorder flag was set by the user
We want to take different actions if the reorder flag was set by the user or filled by the default value. Thus, we propagate this information from build to the krusty options. Signed-off-by: Yannis Zarkadas <yanniszark@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 88f80cd - Browse repository at this point
Copy the full SHA 88f80cdView commit details -
api/krusty: Ensure sort ordering works with CLI flag and kustomization
Sort order can be defined in two places: - (new) kustomization file - (old) CLI flag We want the kustomization file to take precedence over the CLI flag. Eventually, we may want to move away from having a CLI flag altogether: kubernetes-sigs#3947 Case 1: Sort order set in kustomization file AND in CLI flag. Print a warning and let the kustomization file take precedence. Case 2: Sort order set in CLI flag only or not at all. Follow the CLI flag (defaults to legacy) and reorder at the end. Case 3: Sort order set in kustomization file only. Simply build the kustomization. Signed-off-by: Yannis Zarkadas <yanniszark@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 6143039 - Browse repository at this point
Copy the full SHA 6143039View commit details -
krusty: Add e2e test for SortOrderTransformer
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
Configuration menu - View commit details
-
Copy full SHA for 202768f - Browse repository at this point
Copy the full SHA 202768fView commit details -
plugins: Purge LegacyOrderTransformer
Signed-off-by: Yannis Zarkadas <yanniszark@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for a05b8fb - Browse repository at this point
Copy the full SHA a05b8fbView commit details -
Signed-off-by: Yannis Zarkadas <yanniszark@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 4e0cb79 - Browse repository at this point
Copy the full SHA 4e0cb79View commit details -
Signed-off-by: Yannis Zarkadas <yanniszark@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for e581778 - Browse repository at this point
Copy the full SHA e581778View commit details