Repository navigation
v0.16.2
v0.16.2
Before upgrading, check that the network field of every cluster in your InputManifests
belongs to an RFC 1918 private range (10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16).
The field is immutable, so clusters with any other range must be recreated with a valid
range and their workloads migrated.
What's Changed
-
Added Vast.ai as a supported provider #2229
Vast.ai requires a personal API key, a team API key is optional. Vast.ai can only be used
for compute nodepools, not for control plane or load balancer nodepools. -
Added
vramparameter tomachineSpec, allmachineSpecfields are now required for Vast.ai nodepools #2231 -
Cluster VPN
networkranges must be valid IPv4 CIDRs within an RFC 1918 private range #2234Any changes to an InputManifest are rejected until the
networkfield contains a valid range. -
Postpone
unattended-upgradesto 1-3 hours after VM boot to avoid apt lock clashes withkube-eleven#2233 -
General maintenance dependencies update #2243
Bug fixes
- Fixed the operator ClusterRole missing the
eventsresource from theevents.k8s.ioAPI group #2236 - Fixed InputManifest validation to reject OVH, Verda and CloudRift providers for control plane and load balancer nodepools #2239
- Fixed manager scheduling removal of control plane nodes that would break the quorum of healthy nodes #2238