Azure AKS (changelog)

azure/aks last check 242 releases
Notes
no notes yet
Release notes
view on github
2019-08-26 · Release 2019-08-26 · 1y+

This release is rolling out to all regions

  • Features
  • Bug Fixes
    • Fixed bug with older 1.8 clusters that was preventing clusters from upgrading.
      • Important: this was a best effort fix since these cluster versions are out of support. Please upgrade to a currently supported version
      • For information on how AKS handles Kubernetes version support see: Supported Kubernetes versions in Azure
    • Removed the default restricted Pod Security Policy to solve race condition with containers not seeing the user in their config. This policy can be applied by customers.
    • Fixed a bug with kube-proxy, ip-masq-agent and kube-svc-redirect where in certain scenarios they could try to access iptables at the same time.
  • Preview Features
    • CLI extension updated for new Standard Load Balancer (SLB) and VM Scale Set (VMSS) Parameters:
      • --vm-set-type Agent pool vm set type. VirtualMachineScaleSets or AvailabilitySet.
      • --load-balancer-sku - Azure Load Balancer SKU selection for your cluster. Basic or Standard.
      • --load-balancer-outbound-ip-prefixes - Comma-separated public IP prefix resource IDs for load balancer outbound connection. Valid for Standard SKU load balancer cluster only.
      • --load-balancer-outbound-ips - Comma-separated public IP resource IDs for load balancer outbound connection. Valid for Standard SKU load balancer cluster only.
      • --load-balancer-managed-outbound-ip-count - Desired number of automatically created and managed outbound IPs for load balancer outbound connection. Valid for Standard SKU load balancer cluster only.
  • Behavioral Changes
    • Starting from 2019-09-18, the preview CLI extension will default new cluster creates to VM Scale-Sets and Standard Load Balancers (VMSS/SLB) instead of VM Availability Sets and Basic Load Balancers (VMAS/BLB).
    • Starting from 2019-11-04 the official CLI and Azure Portal will default new cluster creates to VMSS/SLB instead of VMAS/BLB.
    • These client defaults changes are important to be aware of due to:
      • SLB will automatically assign a public IP to enable egress. This is a requirement placed by Azure Standard Load Balancers, to learn more about Standard vs. Basic, read here.
      • SLB enables bringing your own IP address to be used, you will be able to define these with new parameters.
      • The capability to use an SLB without any public IP assigned is on the roadmap plan.
      • You may still provision a basic load balancer by specifying "basic" for the "loadbalancersku" property at cluster create time.
      • Read more at https://aka.ms/aks/slb
  • Component Updates