Support for Gateway API .

[Coder63]

I'm running Gateway API v1.1.0 & Nginx Gateway Fabric v1.3.0. I'm following this example- https://docs.nginx.com/nginx-gateway-fabric/how-to/traffic-management/client-settings/ to test it out.

Gateway.yaml

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: gateway
spec:
  gatewayClassName: gke-l7-rilb
  listeners:
  - name: http
    port: 80
    protocol: HTTP
    hostname: "*.example.com"

My clientsettingspolicy.yaml

apiVersion: gateway.nginx.org/v1alpha1
kind: ClientSettingsPolicy
metadata:
  name: gateway-client-settings
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: Gateway
    name: gateway
  body:
    maxSize: "10" # sizes without a unit are bytes.

I don't see any status /Accepted for the clientsettingspolicies.gateway.nginx.org.

$ kubectl describe clientsettingspolicies.gateway.nginx.org gateway-client-settings -n foobar

Name:         gateway-client-settings
Namespace:    foobar
Labels:       <none>
Annotations:  <none>
API Version:  gateway.nginx.org/v1alpha1
Kind:         ClientSettingsPolicy
Metadata:
  Creation Timestamp:  2024-07-29T18:18:08Z
  Generation:          1
  Managed Fields:
    API Version:  gateway.nginx.org/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
      f:spec:
        .:
        f:body:
          .:
          f:maxSize:
        f:targetRef:
          .:
          f:group:
          f:kind:
          f:name:
    Manager:         kubectl-client-side-apply
    Operation:       Update
    Time:            2024-07-29T18:18:08Z
  Resource Version:  557991295
  UID:               65e7fcb6-9672-43da-9e23-097251e74f35
Spec:
  Body:
    Max Size:  10
  Target Ref:
    Group:  gateway.networking.k8s.io
    Kind:   Gateway
    Name:   gateway
Events:     <none>

how can I start troubleshooting this issue ? Appreciate any help on this ..

[sjberman]

@Coder63 I see you have gatewayClassName: gke-l7-rilb specified in your Gateway resource. This should be pointing at the GatewayClass that you deployed for NGINX Gateway Fabric, which is named nginx by default (it gets deployed as part of the default installation for NGF).

[Coder63]

@sjberman : Thanks !! Few more questions , please

1. Right now different/ GKE gatewayClass : gke-l7-rilb are supported ? I'm have Kubernetes Gateway API object gateway& HTTP Route. Trying to extend NGF CRD's to add these ClientSettingsPolicy.

2. What is the intention of having targetRef group pointing to Kubernetes Gateway API CRD's object ?

  targetRef:
    group: gateway.networking.k8s.io
    kind: Gateway
    name: gateway

[sjberman]

The NGINX Gateway Fabric Deployment has to be linked to a GatewayClass that specifies the proper controllerName. The nginx GatewayClass has controllerName: gateway.nginx.org/nginx-gateway-controller specified and the Deployment has the --gateway-ctlr-name=gateway.nginx.org/nginx-gateway-controller command-line flag to match.

If you want to use the GKE GatewayClass, you'll need to update the controllerName. Though there really isn't much reason to do so since you can use the existing nginx GatewayClass.

The targetRef specifies at which level to attach the ClientSettingsPolicy. Attaching to the Gateway means that all Routes under that Gateway will inherit the settings defined in that Policy.