Updates gateway-class-config docs to include fields for privileged co…

…ntainer port-mapping and Openshift Security Context Constraints

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

website/content/docs/api-gateway/configuration/gatewayclassconfig.mdx

@@ -38,7 +38,9 @@ The following outline shows how to format the configurations in the `GatewayClas
   * [`consulAPIGateway`](#image-consulapigateway): string | optional
   * [`envoy`](#image-envoy): string | optional
 * [`logLevel`](#loglevel): string | optional
+* [`matchPrivilegedContainerPorts`](#matchPrivilegedContainerPorts): integer | optional
 * [`nodeSelector`](#nodeselector): string | optional
+* [`openshiftSCCName`](#openshiftSCCName): string | optional
 * [`serviceType`](#servicetype): string | optional
 * [`useHostPorts`](#usehostports): boolean | optional
 
@@ -152,12 +154,27 @@ You can specify the following strings:
 * `debug`
 * `trace`
 
+### matchPrivilegedContainerPorts
+```suggestion
+Specifies a value that Consul adds to privileged ports defined in the gateway. Privileged ports are port numbers less than 1024 and some platforms, such as Red Hat OpenShift, explicitly configure Kubernetes to avoid running containers on privileged ports. The total value of the configured port number and the `matchPriviledgedContainerPorts` value must not exceed 65535, which is the highest possible TCP port number allowed.
+for gateway containers
+* Type: Integer
+* Required: optional
+
+You can specify an integer between `0` and `64512`
+
 ### nodeSelector
 Pods normally run on multiple nodes. You can specify a set of parameters in the `nodeSelector` that constrain the nodes on which the pod can run, enabling the pod to fit on a node. The selector must match a node's labels for the pod to be scheduled on that node. Refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) for additional information.
 
 * Type: string
 * Required: optional
 
+### openshiftSCCName
+Specifies the OpenShift security context constraint (SCC) for the `GatewayClassConfig` to use. Refer to the [OpenShift SCC documentation](https://docs.openshift.com/container-platform/4.13/authentication/managing-security-context-constraints.html#default-sccs_configuring-internal-oauth) for additional information about the available default SCCs.
+* Type: string
+* Required: optional
+* Default: `restricted-v2`
+
 ### serviceType
 Specifies the ingress methods for the gateway's Kubernetes service.
 * Type: string