blob: e751f0bf4fcf2a7c5f689dd90d1e6a8560b8d5d1 [file]
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-bookworm
image-project: debian-cloud
image-family: debian-12
username: zuul
key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDaTT3+Y6dIh221ZsQ0ki6VwGb6lzd1/CvIS8RX6ZNmxJTXS7UKlvhAVTbGQPtmjdIQbwUyEqZEvIm/bUBr7dNbyeMLiRiRtoN+u1Quq8OAes2N7nUKnjLjGjVnM2mvYHGWHRDbpAQCtmXtbiQkHkfLLzewb+MqntQZ57xap31qriTkv4rdnlMN4kElILb5E/8WOAAJXYrt3b1TrTXwZUx7is1OTa38I9jJTpUMCn2otWGH9LlfeUhz/z8ZPB21wgUZN9CF5NwwBanqCNXy0jHiumOGx9e7Hc7apt641KiDuRt0aWyE6No/aMe6hVYnFR3NMG3rBtortXl+R5birK8l zuul
pools:
- name: main
max-servers: 1
use-internal-ip: True
# Gate node readiness on SSH/host-key-scan reachability
# (nodepool's GCE default). With this enabled nodepool verifies a node
# is SSH/host-key-scan reachable before handing it to the executor, and
# relaunches nodes that never become reachable. This relies on
# the launcher being able to reach the node internal IP, which
# is how this deployment is configured. It was
# previously disabled to dodge a GCE baked-in-host-key race
# (the image host key is regenerated a few seconds into boot);
# that removed the readiness gate and let the executor receive
# not-yet-SSH-ready nodes, causing intermittent RETRY_LIMIT
# (~1/3 of builds; see issue 502048297). On this Debian image
# serial output shows host keys are regenerated before sshd
# binds, so a post-sshd ssh-keyscan should capture the
# regenerated key, not the baked-in one. Validate the
# RETRY_LIMIT rate post-merge; roll back if host-key-scan
# failures appear in the launcher log.
host-key-checking: True
labels:
- name: debian-bookworm-8G
instance-type: n1-standard-2
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-30G
instance-type: n1-standard-8
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-60G
instance-type: n1-standard-16
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-n1-standard-2
instance-type: n1-standard-2
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-n1-standard-8
instance-type: n1-standard-8
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-n1-standard-16
instance-type: n1-standard-16
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-e2-standard-2
instance-type: e2-standard-2
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-e2-standard-8
instance-type: e2-standard-8
cloud-image: debian-bookworm
volume-size: 40
- name: debian-bookworm-e2-standard-16
instance-type: e2-standard-16
cloud-image: debian-bookworm
volume-size: 40
labels:
- name: debian-bookworm-8G
min-ready: 0
- name: debian-bookworm-30G
min-ready: 0
- name: debian-bookworm-60G
min-ready: 0
- name: debian-bookworm-n1-standard-2
min-ready: 0
- name: debian-bookworm-n1-standard-8
min-ready: 0
- name: debian-bookworm-n1-standard-16
min-ready: 0
- name: debian-bookworm-e2-standard-2
min-ready: 0
- name: debian-bookworm-e2-standard-8
min-ready: 0
- name: debian-bookworm-e2-standard-16
min-ready: 0