Kubernetes version upgrade

About

You may receive notification from Microsoft that the version of Kubernetes in Azure that your Templafy Email Signature Server cluster is running will be deprecated. Upgrading the Kubernetes version is recommended to ensure continued support from Microsoft for your Azure Kubernetes Services cluster.

• Pre-requisites
• Upgrade Kubernetes in the Azure portal
• Upgrade the Horizontal Pod Autoscaler version
• Additional resources

Pre-requisites

Upgrade Kubernetes in the Azure portal

You may upgrade the Kubernetes version for the cluster at any time by navigating to the templafyemailsignatureserver Kubernetes service in the Resource group for the cluster.

1. Click the current Kubernetes version link on the Overview of the templafyemailsigantureserver Kubernetes service
   
   

   
   
   

2. Click the "Upgrade version" link
3. Select the Kubernetes version to upgrade to in the right-hand pane
4. Leave the default "Upgrade control plane + all node pools" radio button set
5. Click [Save]
   

   

Upgrade the Horizontal Pod Autoscaler version

1. Get access to Kubernetes cluster using Bash Cloud Shell.

   • Log in to Azure portal.

   • Start Cloud Shell 

   • Verify subscription where the AKS cluster for Templafy Email Signature Server resides.

     az account show

     

     • If needed, set the Enabled subscription to the one where the Templafy ESS AKS cluster resides.
       az account set --subscription SUBSCRIPTION_NAME_OR_ID

   • Run the commands to authenticate to the AKS cluster.

     Replace "RESOURCE_GROUP_NAME" with the Resource group name that contains your templafyemailsignatureserver Kubernetes service resource.

     • az aks get-credentials --name templafyemailsignatureserver --resource-group RESOURCE_GROUP_NAME
     • kubectl get ns

       This may trigger an SSO Microsoft authentication process. Follow the instructions on screen and after successful authentication the output will be the namespaces of the cluster.

       Now you have a valid session with the cluster to run the rest of the commands below.
2. Get the HPA NAME and NAMESPACE.

   • kubectl get hpa --all-namespaces

     

3. Get the current HPA configuration by running the following commands and replace "NAME" with the name of the HPA and "NAMESPACE" with the namespace.
   • kubectl get hpa NAME --namespace NAMESPACE -o yaml
4. If "apiVersion: autoscaling/v2" is present, you are all set! Otherwise continue this guide to set this configruation...
5. Get the current HPA configuration as a yaml file  for editing.
   • kubectl get hpa NAME --namespace NAMESPACE --output yaml > hpa.yaml
6. Edit the hpa.yaml file in a text editor.
   • code hpa.yaml
7. Find the apiVersion top-level entry in the file and update it to the string for the new API version "autoscaling/v2", if it is not already set.

   

8. If the top-level apiVersion entry is missing it will need to be added as the very first line as shown above.
   • NOTE: There may be another "apiVersion: apps/v1" entry under the "scaleTargetRef:" section. This entry can be ignored and is not modified.

     

9. Save the changes in the hpa.yaml file.
   • Ctrl-S in the editor window, or use the menu in the upper right of the code editor
10. Apply the updated configuration
    • kubectl apply --filename hpa.yaml
11. Verify that the HPA is running and using the new API version by running the following command and replace "NAME" with the name of the HPA and "NAMESPACE" with the namespace. Look for the apiVersion field in the output and ensure that it matches the version "autoscaling/v2".
    • kubectl get hpa NAME --namespace NAMESPACE -o yaml

Additional resources

You may also review the published Microsoft support article sections for this upgrade to gain more detailed background information and to find the actions to perform the upgrade on the command line.