Is Gateway's spec.addresses field supported?

[sbar95]

Hi Team,

Is Gateway's spec.addresses field supported by kong-operator? And if not, is it planned to be?

---

I got a usecase where an internal Gateway serves traffic from within the cluster.
I apply such manifests to achieve this:

Manifests

apiVersion: gateway-operator.konghq.com/v1beta1
kind: GatewayConfiguration
metadata:
  name: kong-ts
  namespace: gateway-controller
spec:
  dataPlaneOptions:
    deployment:
      podTemplateSpec:
        spec:
          containers:
          - name: proxy
            image: kong:3.9.1
    network:
      services:
        ingress:
          type: ClusterIP
  controlPlaneOptions:
    deployment:
      podTemplateSpec:
        spec:
          containers:
          - name: controller
            image: kong/kubernetes-ingress-controller:3.5.2
---
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: kong-ts
spec:
  controllerName: konghq.com/gateway-operator
  parametersRef:
    group: gateway-operator.konghq.com
    kind: GatewayConfiguration
    name: kong-ts
    namespace: gateway-controller
---
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: kong-ts
  namespace: gateway-controller
spec:
  gatewayClassName: kong-ts
  listeners:
  - name: http
    protocol: HTTP
    port: 80
  addresses:
  - type: IPAddress
    value: 172.16.47.251 # address from cluster's service network address range

The Gateway and its Kong components are created successfully but the spec.addresses field of Gateway is not honored - the Gateway gets a different ip address:

Check Gateway address

$ kubectl describe gateway kong-ts -n gateway-controller
Name:         kong-ts
Namespace:    gateway-controller
Labels:       <none>
Annotations:  <none>
API Version:  gateway.networking.k8s.io/v1
Kind:         Gateway
Metadata:
  ...
Spec:
  Addresses:
    Type:              IPAddress
    Value:             172.16.47.251
  Gateway Class Name:  kong-ts
  Listeners:
    ...
Status:
  Addresses:
    Type:   IPAddress
    Value:  172.16.44.221
  Conditions:
...

$ kubectl get svc dataplane-ingress-kong-ts-d8z66-x2qsc -n gateway-controller 
NAME                                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
dataplane-ingress-kong-ts-d8z66-x2qsc   ClusterIP   172.16.44.221   <none>        80/TCP    114m

[pmalek]

👋

I believe what you're looking for is tracked in #63 (and is tested via an upstream conformance test: https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/tests/gateway-static-addresses.go).

We currently don't have a concrete timeline to provide this feature.