4 Commits (fd1527a9775f686b2a96efadaa050596910348b8)

Author	SHA1	Message	Date
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
Jacob Tanenbaum	13afa70c81	Implemented both the dry run and local flags. ... Added test cases to show that both flags are operating as intended. Removed the print statement "running in local mode" as in PR#35112 The previous attempt at the PR (PR#35050) was reverted for causeing a flake. I believe that setting the deployments terminationGracePeriodSeconds to 0 should take care of it. I ran hack/make-rules/test-cmd.sh 50 times in a row without encountering the flake	2016-11-03 12:55:19 -04:00