-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Feature: Improve robustness and capabilities of variable inlining #1208
Conversation
427948a
to
b6bd23a
Compare
gentle quick to retriger build |
ccb9ce7
to
b0f0a4f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice tests!
@monopole We were really happy to be able to use kustomize as an improvement over one of the component of our product architecture. To give more better understanding of what we are trying to achieve, we joined three examples of the usage of that feature. In each case, in order to respect the yaml syntax, we could not do:
we had to use a more convoluted struct
Here are the examples:
|
9d947fd
to
43778e3
Compare
/assign @monopole |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jbrette The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
76f3d57
to
435cb7e
Compare
de0bb12
to
485fd21
Compare
1e6a186
to
6541fb1
Compare
@monopole / @Liujingfang1 Apologies for the repeated pings over the last few months but, is there any chance either of you will be giving this or #1217 a review before the end of the year? |
15ff784
to
71d0075
Compare
de8337d
to
960a05f
Compare
- Makefile needs to be updated after change in kustomize organization - Remove mdrip, blackfriday from kustomize dependencies
- Streamline inline implementation, no need for new fields - Upgrade replaceVars methods to deal with non primitive cases - Add deepCopy when inlining non primitiv types - Add tests showcasing usage of parent-inlining of variable Inline: Add more tests for refvars Inline: Update the recurse inlining test - Seems that order of fieldspec and replacement algorithm is important - Went up to four level4 of redirection, and algorithm seems to work. Inline: Update to account for code reviews. - rename methods. - add more comments. - return errors instead of logging statements. - remove noops. Inline: Add another enhanced inlining, test converage of issue 0952 Inline: Add composition example to inline test. Inline: Update Deployment from extensions/v1beta1 to apps/v1
Seems that PR simplifying the usage of kustomize can't merge. Closing it. |
This PR is addressing the following issue: #1190
It allows add the ability to inline/copy a tree first from one K8s object to another and let the standard kustomize transformation proceed.
This is really useful because it allows the reuse of complex tree structure (for instance PodTemplate) accross K8s object and does not force the user to create one variable per field.