Current version of Kubernetes on Microsoft Azure.
Upgrading Microsoft Azure Kubernetes Services
Azure Kubernetes Service (AKS) makes it simple to deploy a managed Kubernetes cluster in Azure. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. As a hosted Kubernetes service, Azure handles critical tasks like health monitoring and maintenance for you. In addition, the service is free, you only pay for the agent nodes within your clusters, not for the masters.
AKS clusters support Role-Based Access Control (RBAC). An AKS cluster can also be configured to integrate with Azure Active Directory. In this configuration, Kubernetes access can be configured based on Azure Active Directory identity and group membership.
For more information, see, Integrate Azure Active Directory with AKS.
From here I will do a step-by-step Upgrade of a Microsoft Azure Kubernetes Cluster to a newer version and set Azure Monitor alert rule active for the future to get an Alert notification when a colleague is upgrading the AKS Services.
Here you see all the newer versions of Kubernetes.
Upgrading to version 1.11.1 of Kubernetes.
IMPORTANT NOTE :
When upgrading an AKS cluster, Kubernetes minor versions cannot be skipped. For example, upgrades between 1.8.x -> 1.9.x or 1.9.x -> 1.10.x are allowed, however 1.8 -> 1.10 is not. To upgrade, from 1.8 -> 1.10, you need to upgrade first from 1.8 -> 1.9 and then another do another upgrade from 1.9 -> 1.10
KubeCluster Activity Log
At the green arrow on this picture you can download the activities into CSV file. At the Red arrow you see the User ID who initiated the Upgrade of the Kubernetes Cluster. This is important information for Azure Alert monitoring.
10 minutes later Kubernetes Cluster is Upgraded to version 1.11.1
Upgrade is done.
We now do a minor Upgrade of Kubernetes from version 1.11.1 to 1.11.2 to get the newest version on Azure.
Click on 1.11.2 version and hit Save.
Microsoft Azure Monitoring Alerts
When you click on the second activity of the Upgrade you see at arrow 2 that you can add an Activity Log Alert by Azure monitoring.
Creating Rule Alerts.
- Define Alert condition is already set. We want an Alert notification on Upgrading KubeCluster.
- Define Alert details, must be set.
- Define Action Group, must be set to create the Alert Rule.
2. Define the Alert Details.
3. Define Action Group : Click on + New Action Group
Click on OK
Created Action Group name AKSAdmins
An action group is a collection of notification preferences defined by the user. Azure Monitor and Service Health alerts are configured to use a specific action group when the alert is triggered. Various alerts may use the same action group or different action groups depending on the user’s requirements.
More information on Creating and managing action groups in the Azure portal can be found here
For information on how to use Azure Resource Manager templates to configure action groups, see Action group Resource Manager templates.
From here you can Create the Alert Rule and make it Active.
Azure Monitor Alerts with one rule Enabled.
Here is our Active KubeCluster Alert Rule.
Now we will get a notification when a Colleague is Upgrading our KubeCluster in the Future 😉
KubeCluster is now running the latest available version of Kubernetes.
Kubernetes Cluster nodes are Healthy and running version 1.11.2
Here you see in the Kubernetes Dashboard the Node version of Kubernetes.
For Developers and DevOps it’s Great to work with Microsoft Visual Studio Code and the Azure Kubernetes Services (AKS) to work in a CI/CD Pipeline, to create continuous business applications in the Cloud.
Here is my Azure KubeCluster running in Visual Studio Code 🙂
And at last, most important thing is that my Application is running on my Azure Kubernetes Cluster for the Business My Test Site.
Hope this blogpost is useful for you and your business to manage your AKS Cluster in the Microsoft Cloud.