9 Commits (f824b58ba2cc592a24f8b9ca6249cdb263da25ad)

Author	SHA1	Message	Date
Jeff Grafton	7a8696c331	Update to debian-base 0.4.0 ... Additionally, update the addon-manager to use kubectl v1.11.3.	2018-10-19 11:13:28 -07:00
Jeff Grafton	296fe185fa	Update to use debian-base:0.3.2	2018-08-10 15:37:10 -07:00
Satyadeep Musuvathy	025a0b3bf3	Upgrade debian-base to 0.3.1 for CVEs	2018-08-08 16:50:10 -07:00
Matthias Bertschy	9b15af19b2	Update all script to use /usr/bin/env bash in shebang	2018-04-19 13:20:13 +02: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
Ryan Phillips	66965daf56	bump base images to debian stretch	2017-11-10 09:54:10 -06:00
Manjunath A Kumatagi	33b0702edc	Multiarch support for pets images	2017-09-07 22:30:41 +05:30