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
Enable local selection of dependencies #83
Enable local selection of dependencies #83
Changes from all commits
00504af
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.
Could we move this Dockerfile. It is NOT related to deploying this component. It is used to build the go binaries locally.
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.
I don't agree with the mix that we have here. We now have this Dockerfile defined in two places -- the
k8s-test-infra
repo and here with no clear dependencies defined between the two. What causes each of these to change? How do we ensure that these are kept in sync.The original motivation for the k8s-test-infra image was to have a single image to build these components and to be able to reuse that in the CI steps. At the moment, however, we seemt to have moved to native Golang steps -- with the exception of the build step which could also be native in this case.
Could we rather switch to using local images and not depend on
k8s-test-infra
at all?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.
The approach on this Patch was to enable a fall-back option for local development, to enable a developer to try new versions of the same dependencies at will in real-time, without requiring a PR against
k8s-test-infra
to bump a dependency there. I will file a new patch to propose a better solution that still gives us the flexibility of this patch, but centralizes everything atk8s-test-infra
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.
#86
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.
As mentioned before, I would drop these from here and they shouldn't really be configurable on a given branch.
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.
Retracting, given my coment above.
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.
I would still remove them from here and only specify them in the Dockerfile. What motivation is there for keeping them defined here?
If these are "real" dependencies, then we should manage them using something else so that we can better manage the update lifecycle.