77d9512764
The addition of the volume-size attribute necessitates an upgrade to the Azure API. The newer version of the API allows us to remove the individual handling we have for NICs, PIPs, and Disks. That simplifies the driver greatly, but comes with some caveats that are noted in the docs and release notes. Finally, the volume-size attribute is added as well. Change-Id: I6e335318cedbf0ac8944107aff9d1a2cfcab271a
29 lines
1.1 KiB
YAML
29 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
The Azure driver now supports specifying the size of the OS disk.
|
|
upgrade:
|
|
- |
|
|
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).
|