Skip to content

@palma21 palma21 released this Oct 16, 2019 · 1 commit to master since this release

This release is rolling out to all regions

Service Updates

  • With the official 2019-11-04 Azure CLI release, AKS 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).
  • From 2019-10-14 AKS Portal 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). Users can still explicitly
    choose VMAS and BLB.
  • From 2019-11-04 the CLI extension will have a new parameter --zones to replace --node-zones, which specifies the zones to be used by the cluster nodes.

Release Notes

  • Bug Fixes
    • Fixed a bug where nodepool API would not accept and handle empty fields correctly, "", "{}", "{"properties":{}}".
    • Fixed a bug with http application routing addon where portal would lowercase all addon names and the input was not accepted.
    • Upgrade operation will not fail when manual changes have been applied to the SinglePlacementGroup property on underlying VMSS.
    • Fixed bug where customers trying to enable pod security policy without providing k8s version in the request would encounter failure (500 internal error).
    • Fixed bug where NPM pods would consume an excessive amount of memory.
  • Preview Features
    • Updated windows image to the latest version.
  • Component Updates
Assets 2

@palma21 palma21 released this Oct 10, 2019 · 3 commits to master since this release

This release is rolling out to all regions

Service Updates

  • With the official 2019-11-04 Azure CLI release, AKS 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).
  • From 2019-10-14 AKS Portal 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). Users can still explicitly
    choose VMAS and BLB.

Release Notes

  • Behavioral Changes
    • Improved process and speed of upgrade to reduce impact to pods during the process
  • Bug Fixes
    • Fixed a bug where kubelet reserved values where applied only to primary node pool. Now correctly applied to all nodepools if using multiple nodepools.
    • Added additional service principal validation on Upgrade.
    • Prevented multiple concurrent provisioning operations.
  • New Features
    • Kubernetes versions 1.15.4, 1.14.7 and 1.13.11 have been added.
      Component Updates
    • AKS-Engine has been updated to v0.41.4
Assets 2

@jnoller jnoller released this Oct 4, 2019 · 5 commits to master since this release

Release 2019-09-30

This release is rolling out to all regions

Service Updates

  • With the official 2019-11-04 Azure CLI release, AKS 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).
  • Support for node pool taints and public ip assignment per node with AKS will
    be available in Azure CLI extension v0.4.17
  • AKS Availability Zone support has been expanded to the following regions:
    • Japan East
    • UK South
    • France Central
    • East US
    • Central US
    • Australia East

Release Notes

  • New Features
  • Bug Fixes
    • Fix a bug where the removal of an outbound rule from standard load balancer
      in the AKS node resource group could cause the failure of subsequent
      cluster operations.
    • Fixed the issue impacting GPU enabled clusters being unable to install the
      required NVidia drivers.
    • Fixed an issue where customers could encounter a CSE (custom script
      extension) error 99 during operations.
    • Fixed an issue with the Azure Portal cluster metrics multiplying the metric
      count based on the viewed window of time. Moving forward the default for
      these metrics will be correctly set to average() as opposed to sum().
      • For customers with metrics already enabled and in-use in portal, the sum()
        type will continue to be supported.
  • Component Updates
    • AKS-Engine has been updated to v0.40.1
  • Preview Features
    • Fixed an issue where nodes provisioned by cluster autoscaler would be
      de-provisioned when resetting or updating AAD credentials.
Assets 2

@jluk jluk released this Sep 27, 2019 · 13 commits to master since this release

This release is rolling out to all regions

Service Updates

  • Azure CLI 2.0.74 released with key AKS changes
    • https://github.com/Azure/azure-cli/releases/tag/azure-cli-2.0.74
    • Added --load-balancer-sku parameter to aks create command, which allows for
      creating AKS cluster with SLB
    • Added --load-balancer-managed-outbound-ip-count,
      --load-balancer-outbound-ips and --load-balancer-outbound-ip-prefixes
      parameters to aks [create|update] commands, which allow for updating load
      balancer profile of an AKS cluster with SLB
    • Added --vm-set-type parameter to aks create command, which allows to
      specify vm types of an AKS Cluster (vmas or vmss)

Release Notes

  • Bug Fixes
    • Fixed an issue where the node pool count rendered in the portal would be incorrect when not using the multiple node pools feature.
    • Fixed an issue to ensure a cluster upgrade will upgrade both the control plane and agent pools for clusters using VMSS, but not multiple agent pools.
    • Resolved an issue with cluster upgrades that could remove existing
      diagnostics settings and data erroneously.
    • Fixed an issue where AKS was not validating user defined taint formats per agent pool resulting in
      failures at cluster creation time.
  • Behavioral Changes
    • Increased the reserved CPU cores for kubelets to scale proportionally to cores available on the kubelet's host node. Read more about AKS resource reservation here.
  • Preview Features
    • Fixed an issue where AKS was not enforcing the minimum Kubernetes version
      required at additional agent pool creation time when using the multiple node pools feature.
    • Fixed an issue where creating new agent pools will overwrite the route
      table and customers would lose their route table rules. Fixes issue #1212.
Assets 2

@jnoller jnoller released this Sep 23, 2019 · 14 commits to master since this release

This release is rolling out to all regions

Service Updates

  • The announced updates to default new clusters to VMSS/SLB configurations is
    under way, if you are using the aks-preview Azure CLI extension,
    all clusters created are now defaulted to VMSS & SLB.
  • AKS Kubernetes 1.10 support will be end-of-lifed on Oct 25, 2019
  • AKS Kubernetes 1.11 & 1.12 support will be end-of-lifed on Dec 9, 2019
  • New Documentation additions:
  • The AKS team is pleased to announce the new aks-periscope tool.
    • AKS Periscope will allow AKS customers to run initial diagnostics and
      collect logs into an Azure Blob storage account to help them analyze and
      identify potential problems.
    • For more information please see: https://aka.ms/AKSPeriscope

Release Notes

Assets 2

@jnoller jnoller released this Sep 16, 2019 · 21 commits to master since this release

Service Updates

  • AKS Kubernetes 1.10 support will end-of-lifed on Oct 25, 2019

  • AKS Kubernetes 1.11 & 1.12 support will be end-of-lifed on Dec 9th, 2019

    • Kubernetes 1.15 support on AKS will go GA in Oct 2019
    • Post with additional information will be linked.
  • Known issue: Service principal not found: #1206

  • Resolved: AKS workers continually reboot: #1204

  • Kubernetes 1.16 breaking API changes: #1205

  • New Features

  • Bug Fixes

    • Fixed an issue where cluster upgrade could be blocked when the "managedBy"
      property is missing from the node resource group.
    • Fixed an issue where ingress controller network policy would block all
      egress traffic when assigned to pods (using label selectors).
  • Behavioral Changes

    • Review the planned changes for new cluster creation defaults referenced in
      Release 2019-08-26
  • Preview Features

    • Fixed an issue where multiple nodepool clusters would use the incorrect
      version(s) and block upgrades.
    • Fixed an issue where AKS would incorrectly allow customers to specify
      different versions for multiple nodepools.
    • Fixed an issue where the incorrect node count would be returned or fail to
      update when using multiple node pools
Assets 2

@jluk jluk released this Sep 5, 2019 · 25 commits to master since this release

  • Preview Features

    • Kubernetes 1.15 is now in Preview (1.15.3)
  • Bug Fixes

    • A bug where kube-svc-redirect would crash due to an invalid bash line has been fixed.
    • A recent Kubernetes dashboard change to enable self-signed certs has been reverted due to browser issues.
    • A bug where the OMSAgent pod would fail scheduling on a user tainted node has been fixed with proper toleration on the OMSAgent pod.
    • A preview bug allowing more than 8 node pools to be created has been fixed to enforce a max of 8 node pools per cluster.
    • A preview bug that would change the primary node pool when adding a new node pool has been fixed.
  • Behavioral Changes

    • Review the planned changes for new cluster creation defaults referenced in Release 2019-08-26
  • Component Updates

Assets 2

@palma21 palma21 released this Aug 29, 2019 · 28 commits to master since this release

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
Assets 2

@palma21 palma21 released this Aug 21, 2019 · 30 commits to master since this release

This release is rolling out to all regions

Please Note: This release includes new Kubernetes versions 1.13.10 &
1.14.6 these include the fixes for CVEs CVE-2019-9512 and
CVE-2019-9514. Please see our customer guidance

  • Bug Fixes
    • New kubernetes versions released to fix CVE-2019-9512 and CVE-2019-9514
      • Kubernetes 1.14.6
      • Kubernetes 1.13.10
    • Fixed Azure Network Policy bug with multiple labels under a matchLabels selector.
    • Fix for CNI lock timeout issue caused due to race condition in starting telemetry process.
    • Fixed issue creating AKS clusters using supported Promo SKUs
  • Component Updates
Assets 2

@palma21 palma21 released this Aug 16, 2019 · 33 commits to master since this release

This release is rolling out to all regions

  • Bug Fixes

    • Several bug fixes for AKS NodePool creation and other CRUD operations.
    • Fixed audit log bug on older < 1.9.0 clusters.
      • 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
    • Improved error messaging for VM size errors, including actions to take.
    • Fixed for PUT request bug that caused an unexpected API restart.
  • Behavioral Changes

Assets 2
You can’t perform that action at this time.