2015-04-09 21:50:27 +00:00
|
|
|
{
|
|
|
|
|
"kind": "ReplicationController",
|
2015-07-01 06:36:39 +00:00
|
|
|
"apiVersion": "v1",
|
2015-04-09 21:50:27 +00:00
|
|
|
"metadata": {
|
|
|
|
|
"name": "test-controller",
|
|
|
|
|
"namespace": "test",
|
|
|
|
|
"labels": {"name": "test-controller"}
|
|
|
|
|
},
|
|
|
|
|
"spec": {
|
|
|
|
|
"replicas": 0,
|
|
|
|
|
"selector": {"name": "test-pod"},
|
|
|
|
|
"template": {
|
|
|
|
|
"metadata": {
|
|
|
|
|
"namespace": "test",
|
|
|
|
|
"labels": {"name": "test-pod"}
|
|
|
|
|
},
|
|
|
|
|
"spec": {
|
|
|
|
|
"containers": [{
|
|
|
|
|
"name": "test-container",
|
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-01-17 19:36:53 +00:00
|
|
|
"image": "k8s.gcr.io/pause-amd64:3.1"
|
2015-04-09 21:50:27 +00:00
|
|
|
}]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
