2016-04-06 20:14:48 -04:00
|
|
|
apiVersion: extensions/v1beta1
|
2016-01-19 17:50:03 -05:00
|
|
|
kind: Deployment
|
|
|
|
|
metadata:
|
2016-01-28 11:35:14 -05:00
|
|
|
name: nginx
|
2016-01-19 17:50:03 -05:00
|
|
|
labels:
|
2016-01-28 11:35:14 -05:00
|
|
|
name: nginx-undo
|
2016-01-19 17:50:03 -05:00
|
|
|
spec:
|
|
|
|
|
replicas: 3
|
|
|
|
|
selector:
|
2016-02-05 21:43:02 -05:00
|
|
|
matchLabels:
|
2016-01-28 11:35:14 -05:00
|
|
|
name: nginx-undo
|
2016-01-19 17:50:03 -05:00
|
|
|
template:
|
|
|
|
|
metadata:
|
|
|
|
|
labels:
|
2016-01-28 11:35:14 -05:00
|
|
|
name: nginx-undo
|
2016-01-19 17:50:03 -05:00
|
|
|
spec:
|
|
|
|
|
containers:
|
|
|
|
|
- name: nginx
|
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 14:36:53 -05:00
|
|
|
image: k8s.gcr.io/nginx:1.7.9
|
2016-01-19 17:50:03 -05:00
|
|
|
ports:
|
|
|
|
|
- containerPort: 80
|
