KIC defaults to 'kong' despite GatewayClass being set to another name

[jessebye]

Current Behavior

If we set the GatewayClass to a name other than kong, the KIC is not configured correctly and still uses the default of kong. This results in KIC not reconciling expected resources.

We can work around this issue by adjusting the GatewayConfiguration -> controlPlaneOptions -> deployment -> podTemplateSpec -> spec -> containers -> env and setting CONTROLLER_INGRESS_CLASS to the name of our custom GatewayClass.

Expected Behavior

Gateway Operator should set the CONTROLLER_INGRESS_CLASS env variable correctly in the KIC spec.

Steps To Reproduce

1. Install gateway-operator
2. Create a GatewayClass and GatewayConfiguration using a name other than kong.
3. Create custom resources, such as KongConsumer that have to reference the ingress class name.
4. Note that these CRs aren't reconciled.

Operator Version

1.4

kubectl version

Client Version: v1.32.1
Kustomize Version: v5.5.0
Server Version: v1.32.1-eks-8cce635