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.
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 IMAGE_REPO and IMAGE_TAG templated values in custom build and helm deploy #4278
Make IMAGE_REPO and IMAGE_TAG templated values in custom build and helm deploy #4278
Changes from all commits
da14ed6
8a9c1bd
869a3cf
1affdc5
85846d4
fc9056d
a9eac00
1847b96
93eccef
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@tstromberg currently
skaffold render
for helm passes empty values forimage.name
andimage.tag
. Also it skips over--set-file
. Shouldn'tdeploy
andrender
lead to identical kubernetes yaml files? That's what I assumed and extracted the commonconstructOverrideArgs
method. Let me know if that shouldn't be the case.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.
It seems logical to me that deploy and render should yield identical manifests, but there are likely corner cases to be considered. @nkubala - thoughts?
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.
there are some upcoming features to
render
that will shift the paradigms a bit from the conventionaldeploy
flow, but for the most part they should be going through the same code paths so this is fine.