-
Bug
-
Resolution: Unresolved
-
Critical
-
4.19
Description of problem:
When GatewayClass is created on ocp419, ossm3 gets installed and IstioCR gets created. This IstioCR by default has PodDisruptionBudget set to 1 and min scaling set to 1. This prevents nodes from draining when Openshift gets updated to newer version. There is no way to edit the IstioCR so the workaround described in https://issues.redhat.com/browse/OSSM-9071 does not work. Only workaround I found is to remove GatewayClass CR, so IstioCR gets deleted and Openshift update can finish and afterwards recreating GatewayClass CR.
Version-Release number of selected component (if applicable):
ocp 4.19
How reproducible:
Steps to Reproduce:
1. Follow https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/networking/configuring-ingress-cluster-traffic#nw-ingress-gateway-api-enable_ingress-gateway-api to create GatewayClass CR. 2. Openshift cluster has available updates 3. Initiate update and wait. 4. Last step of update is to restart nodes, this will get stuck indefinitely with errors as "Node cannot be drained"
Actual results:
Expected results:
Additional info:
Related: https://issues.redhat.com/browse/OSSM-9071 Will impact RH Connectivity Link users on ocp419.
Potential fixes:
Either:
- By default set in IstioCR spec.values.pilot.autoscaleMin to 2
- By default set in IstioCR spec.values.global.defaultPodDisruptionBudget.enabled to false
- Allow users to change one of these values externally
- blocks
-
OCPBUGS-58394 Service Mesh 3 creates a podDisruptionBudget object that prevents nodes from upgrading
-
- Closed
-
- is cloned by
-
OCPBUGS-58394 Service Mesh 3 creates a podDisruptionBudget object that prevents nodes from upgrading
-
- Closed
-
- links to