-
Bug
-
Resolution: Done
-
Major
-
4.15
-
None
-
No
-
CLOUD Sprint 248, CLOUD Sprint 249
-
2
-
Proposed
-
False
-
We added a carry patch to change the healthcheck behaviour in the Azure CCM: https://github.com/openshift/cloud-provider-azure/pull/72 and whilst we opened an upstream twin PR for that https://github.com/kubernetes-sigs/cloud-provider-azure/pull/3887 it got closed in favour of a different approach https://github.com/kubernetes-sigs/cloud-provider-azure/pull/4891 .
As such in the next rebase we need to drop the commit introduced in 72, in favour of downstreaming through the rebase the change in 4891. While doing that we need to explicitly set the new probe behaviour, as the default is still the classic behaviour, which doesn't work with our cluster architecture setup on Azure.
For the steps on how to do this, we can follow this comment: https://github.com/openshift/cloud-provider-azure/pull/88#issuecomment-1803832076
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- depends on
-
OCPCLOUD-2422 Rebase/update to K8s 1.29 for Cloud Provider Azure
- Closed
- is blocked by
-
OCPCLOUD-2424 Rebase/update to K8s 1.29 for Cluster Cloud Controller Manager Operator
- Closed
- links to