The Zuul team is pleased to announce the release of Zuul 9.1.0.
Download it from PyPI: https://pypi.org/project/nodepool
Find container images at: https://quay.io/organization/zuul-ci
The release notes, included below, are also available in the documentation with hyperlink references:
https://zuul-ci.org/docs/nodepool/9.1.0/releasenotes.html
New Features ============
* The AWS driver now supports an providers.[aws].image-import-timeout option to control automatic retries and timeouts when AWS import task resource limits are reached.
* The AWS driver now supports volume quota. It will automatically register the limits from the cloud and ensure that labels that specify EBS volume attributes stay under the limit.
* The Azure driver now supports specifying the size of the OS disk.
* The Kubernetes and OpenShift drivers now support adding dynamic metadata, i.e. Pod and Namespace labels, with information about the corresponding node request. This is analogous to the existing dynamic tags of the OpenStack, AWS, and Azure drivers.
See providers.[kubernetes].pools.labels.dynamic-labels, providers.[openshift].pools.labels.dynamic-labels, and providers.[openshiftpods].pools.labels.dynamic-labels for details.
* The Azure driver now support specifying community and shared gallery images.
* The metastatic driver will now automatically use the node-attributes from backing nodes as default values for node-attributes of metastatic nodes. Any node-attribute values specified in the metastatic pool config will override those from the backing node.
* An upload timeout can be configured on OpenStack providers for use in the case that image uploads to a provider take longer than the default of one hour.
Upgrade Notes =============
* The Azure driver now uses the "Standard" SKU for all public IP addresses. Previously it would chose either "Standard" or "Basic" depending on the selection of IPv4 or IPv6 addresses.
Pricing for public IP addresses may differ between the SKU levels.
Standard IP addresses block all incoming traffic by default, therefore the use of a Network Security Group is required in order to allow incoming traffic.
If you are not currently using a Network Security Group, then before upgrading Nodepool it is recommended to create one, add any required rules, and attach it to the subnet that Nodepool uses.
* The Azure driver no longer creates and deletes Disks, Network Interfaces, or Public IP Addresses as separate steps.
Nodepool and user-supplied tags will no longer be applied to Network Interfaces, or Public IP Addresses. This also limits Nodepool's ability to detect leaks of these resources (however this is unlikely since Azure is now responsible for deleting them).