11 Commits

Author	SHA1	Message	Date
Jeff Grafton	8495f7c9ed	bazel: add docker_push rules	2019-03-06 12:35:33 -08:00
Jeff Grafton	d7c2c2a606	bazel: refactor multi-arch container builds into starlark	2019-03-06 11:40:33 -08:00
Jeff Grafton	c98b3edb88	bazel: make conformance and hyperkube images multiarch	2019-03-03 21:09:22 -08:00
Jeff Grafton	e216995ef1	Update repo-infra, bazel-skylib, rules_docker, and rules_go dependencies ... Also require bazel 0.18.0+	2019-02-12 17:55:10 -08:00
Jeff Grafton	2d46adaec4	Use debian-hyperkube-base:0.11.0 and remove qemu registration	2018-10-16 14:01:23 -07:00
Jeff Grafton	c34cbb2f70	Bazel: stop using deprecated docker_ rules and turn on stamping	2018-10-12 13:16:38 -07: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
Tim Hockin	e9dd8a68f6	Revert k8s.gcr.io vanity domain ... This reverts commit eba5b6092a. Fixes https://github.com/kubernetes/kubernetes/issues/57526	2017-12-22 14:36:16 -08:00
Tim Hockin	eba5b6092a	Use k8s.gcr.io vanity domain for container images	2017-12-18 09:18:34 -08:00
Maru Newby	adc338d330	Remove all traces of federation	2017-10-26 13:37:37 -07:00
Jeff Grafton	01252967f1	Build hyperkube image with Bazel	2017-09-21 14:30:41 -07:00