Upgrade AKS to 1.25.5 from 1.24.x
All Submissions:
- [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
- [YES] I have updated the documentation accordingly.
- [YES] My code follows the code style of this project.
Current Behavior or Linked Issues
- AKS running in v1.24.4 which has being deprecated by Microsoft.
- The condition Which was added in 772 is not working as skip is not a parameter which is being passed and throwing below error
Job Build_service_resources_dev: Step specifies condition and(succeeded(), not(coalesce(variables.SKIP_TESTS, ))) which is not valid. Reason: Unexpected symbol: ')'. Located at position 53 within expression: and(succeeded(), not(coalesce(variables.SKIP_TESTS, ))). For more help, refer to https://go.microsoft.com/fwlink/?linkid=842996
Does this introduce a breaking change?
-
[YES]
-
This will upgrade the aks from 1.24.x to 1.25.x. Some of the API versions are deprecated which were already stated in the document
-
azurerm_kubernetes_service_versions is introduced to fetch the latest patch version given the major.minor version
-
zones are modified to resolve the issue 777#note_199389 since the public Ip either accept the single zone or it will be created as zone redundandant. It will not accept 2 zones so modified the gateway zones to include all the 3 zones. more info azure-public-ip-availability-zone. These scripts are tested in dev environment using multiple runs and they are success
-
Changed the parameter from
skip
toskipTests
Since skip is not a parameter. resolving the issues in MR 772
Other information
- AKS Upgrade from 1.24.0 to 1.25.5 ( check for available upgrades )
-
AKS Upgrade WARN: Kubernetes has removed objects from ApiGroups between version 1.24.0 and 1.25.5. If you have any resources calling the ApiGroups below, migrate them to new ApiGroups ahead of time to avoid impact learn more here
- CronJob - batch/v1beta1
- EndpointSlice - discovery.k8s.io/v1beta1
- Event - events.k8s.io/v1beta1
- HorizontalPodAutoscaler - autoscaling/v2beta1
- PodDisruptionBudget - policy/v1beta1
- PodSecurityPolicy - policy/v1beta1
- RuntimeClass - node.k8s.io/v1beta1
WARN: AKS upgrade may fail because of the Pod Disruption Budgets set up in AKS for various components. Please make sure that ALLOWED DISRUPTIONS for every PDB in cluster is great than or equals to 1. For more info refer below
resolves issue 252