mirror of
https://github.com/optim-enterprises-bv/kubernetes.git
synced 2025-12-15 20:37:39 +00:00
3586986416
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.
38 lines
1.0 KiB
YAML
38 lines
1.0 KiB
YAML
kind: Deployment
|
|
apiVersion: extensions/v1beta1
|
|
metadata:
|
|
name: calico-node-vertical-autoscaler
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: calico-node-autoscaler
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
spec:
|
|
replicas: 1
|
|
template:
|
|
metadata:
|
|
labels:
|
|
k8s-app: calico-node-autoscaler
|
|
annotations:
|
|
scheduler.alpha.kubernetes.io/critical-pod: ''
|
|
spec:
|
|
containers:
|
|
- image: k8s.gcr.io/cpvpa-amd64:v0.6.0
|
|
name: autoscaler
|
|
command:
|
|
- /cpvpa
|
|
- --target=daemonset/calico-node
|
|
- --namespace=kube-system
|
|
- --logtostderr=true
|
|
- --poll-period-seconds=30
|
|
- --v=2
|
|
- --config-file=/etc/config/node-autoscaler
|
|
volumeMounts:
|
|
- name: config
|
|
mountPath: /etc/config
|
|
volumes:
|
|
- name: config
|
|
configMap:
|
|
name: calico-node-vertical-autoscaler
|
|
serviceAccountName: calico-cpva
|