Skip to content
This repository was archived by the owner on Sep 4, 2024. It is now read-only.

Latest commit

 

History

History
43 lines (30 loc) · 2.45 KB

009a-cluster-upgrades.md

File metadata and controls

43 lines (30 loc) · 2.45 KB

Cluster Upgrades

Kubernetes frequently gets patches and upgrades, addressing security vulnerabilities and adding new functionality. Additionally, AKS releases patches for the underlying node operating system on a regular basis (aka Node Image Updates). You need to implement a process to upgrade the cluster.

Pre-requisites

Make sure the following are complete before setting up ingress.

  • Cluster is provisioned and accessible via 'kubectl'
  • App Deployment is complete

Upgrade Requirements

  • Initial testing should use a manual upgrade process
  • The UI running pod count should be increased to 2
  • The UI pod count should never go below 1 during an upgrade
  • Day 1 (simulated): Due to a critical OS level CVE you've been asked to upgrade the system pool NODE IMAGE ONLY
  • Day 2 (simulated): Due to a critical Kubernetes level CVI you've been asked to upgrade the control plane and the system pool Kubernetes version to the next incremental version (major or minor)
  • Day 3 (simulated): To take advantage of some new Kubernetes features you've been asked to upgrade the user pool Kubernetes version to the next incremental version (major or minor)

Tasks:

  1. Increase the Red Dog UI deployment replica count to 2

  2. Deploy the necessary config to ensure the UI pod count never dips below 1 pod

  3. Check the available upgrade versions for Kubernetes and Node Image

  4. Upgrade the system pool node image

  5. Upgrade the AKS control plane and system pool Kubernetes version

  6. Upgrade the user pool Kubernetes version

    Bonus Tasks:

  7. Enable Automatic Upgrades to the 'patch' channel and set a Planned Maintenance Window (preview) for Saturdays at 1am

Useful links: