blob: beca1bce4a4969518929e7390c4889744856ce77 [file] [log] [blame]
diskimages: []
zookeeper-servers:
- host: zookeeper.zookeeper
port: 2281
zookeeper-tls:
ca: /tls/client/ca.crt
cert: /tls/client/tls.crt
key: /tls/client/tls.key
providers:
- name: gcloud-provider
driver: gce
project: gerritcodereview-ci
region: us-central1
zone: us-central1-a
boot-timeout: 120
cloud-images:
- name: debian-buster
image-project: debian-cloud
image-family: debian-10
username: zuul
key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDaTT3+Y6dIh221ZsQ0ki6VwGb6lzd1/CvIS8RX6ZNmxJTXS7UKlvhAVTbGQPtmjdIQbwUyEqZEvIm/bUBr7dNbyeMLiRiRtoN+u1Quq8OAes2N7nUKnjLjGjVnM2mvYHGWHRDbpAQCtmXtbiQkHkfLLzewb+MqntQZ57xap31qriTkv4rdnlMN4kElILb5E/8WOAAJXYrt3b1TrTXwZUx7is1OTa38I9jJTpUMCn2otWGH9LlfeUhz/z8ZPB21wgUZN9CF5NwwBanqCNXy0jHiumOGx9e7Hc7apt641KiDuRt0aWyE6No/aMe6hVYnFR3NMG3rBtortXl+R5birK8l zuul
pools:
- name: main
max-servers: 4
use-internal-ip: True
# Host key checking is disabled because:
# 1) We're using the internal IP so it's slightly less
# valuable (fewer attack vectors).
# 2) The images we're using appear to have a key baked into
# them which is overwritten at boot. Because we're using the
# internal IP, nodepool can end up connecting to the instance
# very quickly and retrieving the original host key rather
# than the new one (which is likely to be written a couple of
# seconds later). By disabling this in nodepool, we let Zuul
# just use the first key it finds (and it's likely to take
# long enough that it will have been updated by then).
host-key-checking: False
labels:
- name: debian-buster-8G
instance-type: n1-standard-2
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-30G
instance-type: n1-standard-8
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-60G
instance-type: n1-standard-16
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-n1-standard-2
instance-type: n1-standard-2
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-n1-standard-8
instance-type: n1-standard-8
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-n1-standard-16
instance-type: n1-standard-16
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-e2-standard-2
instance-type: e2-standard-2
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-e2-standard-8
instance-type: e2-standard-8
cloud-image: debian-buster
volume-size: 40
- name: debian-buster-e2-standard-16
instance-type: e2-standard-16
cloud-image: debian-buster
volume-size: 40
labels:
- name: debian-buster-8G
min-ready: 0
- name: debian-buster-30G
min-ready: 0
- name: debian-buster-60G
min-ready: 0
- name: debian-buster-n1-standard-2
min-ready: 0
- name: debian-buster-n1-standard-8
min-ready: 0
- name: debian-buster-n1-standard-16
min-ready: 0
- name: debian-buster-e2-standard-2
min-ready: 0
- name: debian-buster-e2-standard-8
min-ready: 0
- name: debian-buster-e2-standard-16
min-ready: 0