7 Commits (7d7df52691513e2cfa764fd80d8a0421ce167bb2)

Author	SHA1	Message	Date
Maciej Borsz	496c2cd1bb	Use gcr.io/k8s-testimages/logexporter:v0.1.2.	2018-08-09 13:23:34 +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
zouyee	5f9d931804	[cluster/log-dump] bump daemonset version	2017-10-24 10:30:20 +08:00
Shyam Jeedigunta	80084f0621	Reduce kubectl calls from O(#nodes) to O(1) in cluster logdump	2017-07-31 13:20:53 +02:00
Shyam Jeedigunta	5f8cb3d9ff	Enable logexporter mechanism to dump logs from k8s nodes to GCS directly	2017-07-12 14:39:49 +02:00