-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
Merge proxy_init image with proxyv2 image #17615
Conversation
Part of istio#17518 Benefits: * 1 less image to worry about * Only pull a single image. This means the pull will be finished during the init, rather than during pod startup. This means Envoy can get ready quicker and have less chance of the application starting up before it and failing requests
/retest |
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.
This is great!
Thanks!! I meant to do that and completely forgot. See lack of tests issue
#17199
…On Fri, Oct 4, 2019 at 4:22 PM Romain Lenglet ***@***.***> wrote:
***@***.**** requested changes on this pull request.
This is great!
------------------------------
In tools/istio-docker.mk
<#17615 (comment)>:
> @@ -127,6 +119,7 @@ docker.proxyv2: pilot/docker/envoy_pilot.yaml.tmpl
docker.proxyv2: pilot/docker/envoy_policy.yaml.tmpl
docker.proxyv2: tools/packaging/common/istio-iptables.sh
docker.proxyv2: pilot/docker/envoy_telemetry.yaml.tmpl
+docker.proxyv2: $(ISTIO_DOCKER)/istio-iptables
How about proxy_debug and proxytproxy? You modified the command line in
the injection template, so those images will now break.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17615?email_source=notifications&email_token=AAEYGXLOPNQFD36GWR7SG73QM7F33A5CNFSM4I5RWBN2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCG7WFIY#pullrequestreview-297755299>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEYGXLC3XK5O4IIMK35733QM7F33ANCNFSM4I5RWBNQ>
.
|
@rlenglet github UI is acting weird, everything should be good now. They all need the bash iptables but only proxyv2 needs the golang version |
Yes, you should be good now. |
/retest |
@istio/wg-environments-maintainers please take a look |
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.
Please change back the name - no need to make docker image inconsistent with .deb ( the .sh at the end).
I'm worried about the .so replacement - but let's see how it goes. It's a problem for distroless in general.
|
So it seems the official way to add .deb packages is our friend Bazel... I really hope the base distroless image for Istio proxy will be generated from a different repo ( tools,etc) so we don't add a bazel dep if we have to..). Maybe even do it in the proxy repo, so that proxy builds also generate a distroless-base image where we can just add the agent ? For now it's probably ok to go with your hack of blindly copying all .so files... |
Talked with @costinm , will use |
I think it makes for the proxy repo to produce all repo artifacts (deb packages and docker images). |
/retest failures seem infrastructural |
/retest |
/retest |
/retest |
/test pilot-multicluster-e2e_istio |
/retest |
/retest |
/retest |
@howardjohn: The following test failed, say
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/test-infra repository. I understand the commands that are listed here. |
/retest |
* istio#16223 * istio#16272 * istio#16187 * istio#16466 * istio#16634 * istio#16594 * istio#16666 * istio#16483 * istio#16820 * istio#16842 * istio#16852 * istio#16835 * istio#16863 * istio#16892 * istio#16991 * istio#16957 * istio#17013 * istio#17134 * istio#17155 * istio#17235 * istio#17342 * istio#17477 * istio#17615 * istio#17334 * istio#17708 * istio#17737 * Fix injection template * Fix quoting * Fix test values * Add accidentally deleted affinity
Part of #17518
Benefits:
the init, rather than during pod startup. This means Envoy can get ready
quicker and have less chance of the application starting up before it
and failing requests
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure