Commit Graph

7 Commits

Author SHA1 Message Date
notpad
dcf80e31ac Migrate Kubemark to distroless 2019-11-16 17:49:26 +08:00
Matt Matejczyk
686245b876 Fix base image discrepancy when building kubemark.
There are two ways of building kubemark: 1) via Dockerfile and 2) via
bazel.

In CI/CD tests we use the 1) way and use debian:jessie as the base
image.

But if you build kubemark via bazel it will use the discouraged busybox
base image.

This PR fixes that by using debian:jessie everywehre and pinning exact
sha version to make the kubemark image hermetic.
2019-10-24 10:50:10 +02:00
Jeff Grafton
c34cbb2f70 Bazel: stop using deprecated docker_ rules and turn on stamping 2018-10-12 13:16:38 -07:00
Shyam Jeedigunta
76c1828c1c
Mark kubemark images w/ random tags to avoid race b/w runs 2018-02-08 17:54:01 +01:00
Tim Hockin
3586986416 Switch to k8s.gcr.io vanity domain
This is the 2nd attempt.  The previous was reverted while we figured out
the regional mirrors (oops).

New plan: k8s.gcr.io is a read-only facade that auto-detects your source
region (us, eu, or asia for now) and pulls from the closest.  To publish
an image, push k8s-staging.gcr.io and it will be synced to the regionals
automatically (similar to today).  For now the staging is an alias to
gcr.io/google_containers (the legacy URL).

When we move off of google-owned projects (working on it), then we just
do a one-time sync, and change the google-internal config, and nobody
outside should notice.

We can, in parallel, change the auto-sync into a manual sync - send a PR
to "promote" something from staging, and a bot activates it.  Nice and
visible, easy to keep track of.
2018-02-07 21:14:19 -08:00
Sen Lu
c2bad6e969 Make kubemark push a manual target 2017-10-13 14:08:55 -07:00
Sen Lu
e0bcfd29ac Try to use bazel to build/push kubemark image 2017-10-11 22:11:36 -07:00