-
Notifications
You must be signed in to change notification settings - Fork 53
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
Move pkg/ext-proc -> cmd/ext-proc #368
Move pkg/ext-proc -> cmd/ext-proc #368
Conversation
Hi @tchap. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
- Cache dependencies - Upload only the files needed
fe0dcc0
to
7d712d0
Compare
COPY pkg ./pkg | ||
COPY internal ./internal | ||
COPY api ./api | ||
WORKDIR /src/cmd/ext-proc |
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.
how should we organize the dockerfiles if we want to support multiple applications in the repo? say we add another app under cmd/ for #355?
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 guess you create a separate Dockerfile for each, unless you need all of them in a single image, which you usually don't. But even that is perfectly possible by using a build stage per executable, then copying all the artifacts into the last stage.
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.
If we create a docker file per app, how do you suggest we do it? Using different names at the top level or put the dockerfile in the cmd/app directory?
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 usually create docker/<component>.Dockerfile
, e.g. docker/ExtProc.Dockerfile
. But that is simply what I came up with for my projects.
/lgtm Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, tchap The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Move pkg/ext-proc -> cmd/ext-proc * Rework Dockerfile - Cache dependencies - Upload only the files needed
Related to #348 .
I also took liberty to improve Dockerfile to cache dependencies and not upload 80 MB of data into Docker.