-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.0, 4.19.0
Description of problem:
Azure is retiring the numberOfProbes property (in 2027), so we need to update any CAPZ, 4.16 Terraform or UPI ARM Template usage of numberOfProbes to use probeThreshold instead. I will create a corresponding spike to investigate whether existing infrastructure needs to be updated. I am copying a pasting the email into the codeblock
Support for the Azure Load Balancer property NumberOfProbes is ending You’re receiving this notice because you’re using the property NumberOfProbes in Azure Load Balancer.We’ll be ending support for the Azure Load Balancer property NumberOfProbes on 1 September 2027. To avoid service disruption, upgrade your apps and start using the Azure Load Balancer property ProbeThreshold before that date. Required action Upgrade your apps to API version 2022-05-01 or higher by 1 September 2027 to begin using the ProbeThreshold property. Refer to our documentation to learn more about updating your API.Alternatively, simply stop using NumberOfProbes.
Version-Release number of selected component (if applicable):
Let's backport to most/all supported versions we're installing in order maximize future proofing of clusters and cut down on the noise from warnings.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Create an Azure Load balancer as part of installation and check that probeThreshold is set appropriately. Remove any code usage of numberOfProbes from installer & CAPZ.
Additional info: