-
Notifications
You must be signed in to change notification settings - Fork 8.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
Rebase GLBC on alpine:3.5 #384
Conversation
Coverage decreased (-0.02%) to 46.418% when pulling 1b0a8c18f06b9df49ce4a94ff73e460653dd2909 on timstclair:busybox into a6e3822 on kubernetes:master. |
Review status: 0 of 8 files reviewed at latest revision, 2 unresolved discussions. controllers/gce/Dockerfile, line 15 at r1 (raw file):
Should we leave a MAINTAINER here? controllers/gce/README.md, line 343 at r1 (raw file):
Just curious why wget is preferred. Comments from Reviewable |
@timstclair why not use alpine instead busybox? |
@timstclair Slipped my mind - we need the ca certs because the GLBC is calling out to the GCP api. |
@nicksardo How is this usually solved? always include ca-certs in each image or just mount from the host through |
Review status: 0 of 8 files reviewed at latest revision, 2 unresolved discussions. controllers/gce/Dockerfile, line 15 at r1 (raw file): Previously, csbell (Christian Bell) wrote…
No, the MAINTAINER line is deprecated. We're gradually removing it from all our images. controllers/gce/README.md, line 343 at r1 (raw file): Previously, csbell (Christian Bell) wrote…
busybox (and alpine) ship with wget, but not curl. Comments from Reviewable |
Rebased on alpine & installed ca-certs. I think we should probably prefer alpine for this type of image anyway, since we get better CVE notifications. Since there are no binary dependencies, I don't anticipate any of the alpine issues we've run into in the past (e.g. DNS problems). @glerchundi I think this approach is preferable to mounting the host ca-certificates, since it keeps the environment contained, and doesn't add any host dependencies. |
Coverage decreased (-0.3%) to 46.129% when pulling b2a1f4b2d0d5875f7cb4cd9e6c8b26bf1e46df24 on timstclair:busybox into a6e3822 on kubernetes:master. |
Squashed & rebased. |
All unit tests, e2e ingress tests, and several manual tests (with and without pre-shared certs) were successful. Merging and generating 0.9.2 image. |
/lgtm |
Automatic merge from submit-queue (batch tested with PRs 42734, 42745, 42758, 42814, 42694) Bump glbc version to 0.9.2 Follow up to kubernetes/ingress-nginx#384
For kubernetes/kubernetes#40248
Rebasing on busybox greatly reduces the size of the image. More importantly, it greatly reduces the management burden of keeping the image up-to-date in as all the packages within are updated.
@csbell @nicksardo