Today, we’re excited to announce the preview of Windows Server containers in Azure Kubernetes Service (AKS) for the latest versions, 1.13.5 and 1.14.0. With this, Windows Server containers can now be deployed and orchestrated in AKS enabling new paths to migrate and modernize Windows Server applications in Azure.
Azure Policy allows you to govern your resources on every service exposed to Azure Resource Manager (at the control plane). With this release, Azure Policy goes even deeper into AKS, allowing you to set policies inside AKS clusters on pods, namespaces and ingress. This extends the capability of Azure Policy to get deeper and deeper into Azure services and give you more control over your resources.
Azure Policy support for Azure Kubernetes Service is now available in preview. Azure Policy uniformly applies policies to Azure resources, like Kubernetes clusters, dramatically simplifying the task of initializing and maintaining compliant environments for Kubernetes applications.
Kubernetes-based Event-driven Autoscaling (KEDA), an open source project jointly developed with Red Hat, allows you to auto-scale deployments in K8S in response to events like a Kafka stream, cloud event, etc without relying solely on CPU and memory consumption of containers.
On April 24, 2019, Azure Kubernetes Service (AKS) released Kubernetes 1.13 support in general availability (GA). According to our policy for supported versions, this means that Kubernetes 1.9 support is reaching end of life.
Customers running 1.9 clusters now have 30 days (May 25, 2019) to upgrade to a supported Kubernetes version (1.10, 1.11, 1.12, or 1.13). During this deprecation period, you can continue to create new 1.9.x clusters. But on May 25, 2019, 1.9.x will be removed from the portal and CLI/APIs.