This article is contributed. See the original author and article here.
Welcome to a new year and the first AKS on Azure Stack HCI update in 2022. The January update is now available!
As always, you can also evaluate AKS-HCI any time by registering here. If you do not have the hardware handy to evaluate AKS on Azure Stack HCI you can follow our guide for evaluating AKS-HCI inside an Azure VM: https://aka.ms/aks-hci-evalonazure.
Here are some of the changes you’ll see in the January update:
Kubernetes 1.22 support
We’re delighted to share that AKS-HCI now supports Kubernetes 1.22. Notable new features in Kubernetes 1.22 include Windows enhancements, a new PodSecurity admission feature, API server tracing feature, generic data populators, and more. Learn more
Please note that Kubernetes release 1.22 comes with a number of deprecated APIs. Please migrate to non-deprecated/stable APIs and test your workloads and environments before upgrading your production environments. To read more about the deprecation of old Kubernetes APIs, click here.
Support for AKS on Azure Stack HCI and Windows Server clusters with SDN enabled
With the latest AKS-HCI January release, we support running AKS on Azure Stack HCI and Windows Server clusters with Software Defined Networking (SDN) enabled by using the same external virtual switch. With this support, your AKS-HCI cluster and pods running on a traditional VLAN network will co-exist with SDN VMs running on a SDN logical network or a SDN virtual network.
Improved error messages and new PowerShell warnings for Restart-AksHci and Uninstall-AksHci
January includes updated warnings and a confirmation prompt for both Restart-AksHci and Uninstall-AksHci to prevent unexpected data/configuration loss.
Documentation for fixing certificates after a break
Many of us shut down our deployments (management and target clusters) for the holidays then came back to find our local deployments in an unmanageable state. Under the hood, this is because cluster certificates are rotated every 3-4 days for security reasons.
We have published a series of guides to help get going again after deferred use or maintenance. That includes a guide for:
- Repairing a cluster that has been shutoff for more than 4 days
- Repairing a cluster that hasn’t been used for more than 60 days
- How to recover if the certificate renewal pod enters a crash loop state (rare)
Documentation for getting applications up and running in Kubernetes
There are new docs this month to help get a scoped set of applications up and running in AKS on Azure Stack HCI. Check out our docs for:
- Getting started with OpenFaaS (Functions as a Service) with Azure Kubernetes Service (AKS) on Azure Stack HCI
- Install existing applications with Helm on Azure Kubernetes Service on Azure Stack HCI
- Deploy a Java application with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) on Azure Stack HCI cluster
While not a specific application – we also have a new doc on setting up an ingress controller, which is important for all web apps.
Once you have downloaded and installed the AKS on Azure Stack HCI January 2022 Update – you can report any issues you encounter and track future feature work on our GitHub Project at https://github.com/Azure/aks-hci. And, if you do not have the hardware handy to evaluate AKS on Azure Stack HCI you can follow our guide for evaluating AKS-HCI inside an Azure VM: https://aka.ms/aks-hci-evalonazure.
I look forward to hearing from you all!
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.