-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
Moderate
-
None
-
Rejected
-
False
-
Description of problem:
creating a custom gatewayclass (named other than "openshift-default"), but finally we got two more gatewayclasses in the cluster.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-07-143919
How reproducible:
100%
Steps to Reproduce:
1. enable GatewayAPI feature gate
2. create a custom gatewayclass
$ oc create -f -<<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
kind: GatewayClass
metadata:
name: mygwclass
spec:
controllerName: openshift.io/gateway-controller
EOF
3. wait for a while until OSSM is ready, then check gatewayclass
Actual results:
$ oc get gatewayclass NAME CONTROLLER ACCEPTED AGE istio-remote istio.io/unmanaged-gateway True 3h45m mygwclass openshift.io/gateway-controller True 3h46m openshift-default openshift.io/gateway-controller True 3h45m only the 2nd one "mygwclass" is created by user, other two are created automatically.
Expected results:
not sure if the other two gatewayclasses are required always, if no then they should not be created.
Additional info:
Tested with 4.17 and we got two gatewayclass, still seeing "openshift-default" there. $ oc get gatewayclass NAME CONTROLLER ACCEPTED AGE mygwclass openshift.io/gateway-controller True 9m openshift-default openshift.io/gateway-controller True 8m1s Tested with 4.16 we just got one gatewayclass that created by user $ oc get gatewayclass NAME CONTROLLER ACCEPTED AGE mygwclass openshift.io/gateway-controller True 18m