Gateway API Controller

The Kubernetes Gateway API standardizes traffic routing in Kubernetes clusters. The Gateway Controller manages all Gateway resources. It ensures correct implementation of configurations defined in Gateway resources.

Note: For capabilities (TIBCO BusinessWorks (Containers) and TIBCO Flogo), you can switch from ingress controller to Gateway API Controller and from Gateway API Controller to ingress controller. You can also switch from one Gateway API controller to other Gateway API Controller.
Field Description
Resource Name Name of the resource
Description Description for the resource
Gateway API Controller Name

Name of Gateway API Controller

Example: example.com/gateway-controller
Gateway Name

Name of Gateway resource

Example: example-gateway

Gateway Namespace Namespace in which Gateway resource is created
Host / Domain Name Host name is the fully qualified domain name of a network host.
Section Name (Optional) The name of a section in a Kubernetes resource.

Configure client max body size for Gateway

For the capability application files of larger size, you need to change the default client max body size for the Gateway. To set a default client max body size for the Gateway created during setup, add the following ClientSettingsPolicy:

kubectl apply -n nginx-gateway -f - <<EOF
apiVersion: gateway.nginx.org/v1alpha1
kind: ClientSettingsPolicy
metadata:
  name: gateway-client-settings
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: Gateway
    name: nginx-gateway
  body:
    maxSize: "200m"
EOF