From f112ac8acf40fc7285187dc69af4ffcbae30c8c5 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Thu, 18 Aug 2022 18:21:47 -0600 Subject: [PATCH 01/15] Document cli args and Gateway API compatibility - Add cli args doc - Fix the description of the gateway-ctlr-name cli arg - Add Gateway APi compatibility doc --- cmd/gateway/main.go | 7 +- docs/cli-args.md | 8 ++ docs/gateway-api-compatibility.md.md | 110 +++++++++++++++++++++++++++ 3 files changed, 122 insertions(+), 3 deletions(-) create mode 100644 docs/cli-args.md create mode 100644 docs/gateway-api-compatibility.md.md diff --git a/cmd/gateway/main.go b/cmd/gateway/main.go index 955054725b..0c174ca6eb 100644 --- a/cmd/gateway/main.go +++ b/cmd/gateway/main.go @@ -12,7 +12,8 @@ import ( ) const ( - domain string = "k8s-gateway.nginx.org" + domain string = "k8s-gateway.nginx.org" + namespace string = "nginx-gateway" ) var ( @@ -25,7 +26,7 @@ var ( gatewayCtlrName = flag.String( "gateway-ctlr-name", "", - fmt.Sprintf("The name of the Gateway controller. The controller name must be of the form: DOMAIN/NAMESPACE/NAME. The controller's domain is '%s'.", domain), + fmt.Sprintf("The name of the Gateway controller. The controller name must be of the form: DOMAIN/NAMESPACE/NAME. The controller's domain is '%s'; the namespace is '%s'", domain, namespace), ) gatewayClassName = flag.String( @@ -46,7 +47,7 @@ func main() { MustValidateArguments( flag.CommandLine, - GatewayControllerParam(domain, "nginx-gateway" /* FIXME(f5yacobucci) dynamically set */), + GatewayControllerParam(domain, namespace /* FIXME(f5yacobucci) dynamically set */), GatewayClassParam(), ) diff --git a/docs/cli-args.md b/docs/cli-args.md new file mode 100644 index 0000000000..22ba03f9de --- /dev/null +++ b/docs/cli-args.md @@ -0,0 +1,8 @@ +# Command-line Arguments + +The table belows describes the command-line arguments of the `gateway` binary from the `nginx-kubernetes-gateway` container. + +| Name | Type | Description | +|-|-|-| +|`gateway-ctlr-name` | `string` | The name of the Gateway controller. The controller name must be of the form: `DOMAIN/NAMESPACE/NAME`. The controller's domain is `k8s-gateway.nginx.org`; the namespace is `nginx-ingress`. | +|`gatewayclass`| `string` | The name of the GatewayClass resource. Every NGINX Gateway must have a unique corresponding GatewayClass resource. | diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md new file mode 100644 index 0000000000..2ff58229ca --- /dev/null +++ b/docs/gateway-api-compatibility.md.md @@ -0,0 +1,110 @@ +# Gateway API Compatibility + +This document describes which Gateway API resources NGINX Kubernetes Gateway supports and the extent of that support. + +## Summary + +| Resource | Support Status | +|-|-| +| [GatewayClass](#gatewayclass) | Partially supported | +| [Gateway](#gateway) | Partially supported | +| [HTTPRoute](#httproute) | Partially supported | +| [TLSRoute](#tlsroute) | Not supported | +| [TCPRoute](#tcproute) | Not supported | +| [UDPRoute](#udproute) | Not supported | +| [ReferenceGrant](#referencegrant) | Not supported | +| [Custom policies](#custom-policies) | Not supported | + +## Terminology + +The support status is described using the following words: +- *Supported*. The resource or field is fully supported and conformant to the Gateway API specification. +- *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in the future releases. +- *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in the future releases. + +Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, that will be documented. + +## Resources + +Below we list the resources and the support status of their corresponding fields. + +Note that we don't describe the meaning of each field. For that, please visit the [Gateway API documentation](https://gateway-api.sigs.k8s.io/references/spec/). + +### GatewayClass + +> Status: Partially supported. + +NGINX Kubernetes Gateway supports only a single GatewayClass resource configured via `--gatewayclass` [cli argument](./cli-args.md). + +Fields: +* `spec` + * `controllerName` - supported. + * `parametersRef` - not supported. + * `description` - supported. +* `status` - partially supported. + +### Gateway + +> Status: Partially supported. + +NGINX Kubernetes Gateway supports only a single Gateway resource: it select the Gateway resource among all resources that belong to +NGINX Kubernetes Gateway (i.e. reference NGINX Kubernetes Gateway corresponding GatewayClass). In case of multiple Gateway resources, NGINX Kubernetes Gateway will use a +deterministic conflict resolution strategy: it will choose the oldest resource based on the creation timestamp. If the timestamps are equal, NGINX Kubernetes Gateway will chose the resource that appears alphabetically first based on its namespace and then name. We might support multiple Gateway resources. If you're interested in that support, please share your use case with us. + +Fields: +* `spec` + * `gatewayClassName` - supported. + * `listeners` + * `name` - supported. + * `hostname` - partially supported. Wildcard hostnames like `*.example.com` are not yet supported. + * `port` - partially supported. Allowed values: `80` for HTTP listeners and `443` for HTTPS listeners. + * `protocol` - partially supported. Allowed values: `HTTP`, `HTTPS`. + * `tls` + * `mode` - partially supported. Allowed value: `Terminate`. + * `certificateRefs` - partially supported. The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls` in the same namespace as the Gateway resource. Only a single reference is supported. The Secret must be deployed before the Gateway resource. Secret rotation (watching for updates) is not supported. + * `options` - not supported. + * `allowedRoutes` - not supported. + * `addresses` - not supported. +* `status` - partially supported. + +### HTTPRoute + +> Status: Partially supported. + +Fields: +* `spec` + * `parentRefs` - partially supported. `sectionName` must always be set. + * `hostnames` - partially supported. Wildcard binding is not supported: a hostname like `example.com` will not bind to a listener with the hostname `*.example.com`. However, `example.com` will bind to a listener with the empty hostname. + * `rules` + * `matches` + * `path` - partially supported. Only `PathPrefix` type. + * `headers` - partially supported. Only `Exact` type. + * `queryParams` - partially supported. Only `Exact` type. + * `method` - supported. + * `filters` - not supported. + * `backendRefs` - partially supported. Only a single backend ref. Backend ref `filters` are not supported. NGINX Kubernetes Gateway will use the IP of the Service as a backend, not the IPs of the corresponding Pods. Watching for Service updates is not supported. +* `status` - partially supported. + +### TLSRoute + +> Status: Not supported. + +### TCPRoute + +> Status: Not supported. + +### UDPRoute + +> Status: Not supported. + +### ReferenceGrant + +> Status: Not supported. + +### Custom Policies + +> Status: Not supported. + +Custom policies will be NGINX Kubernetes Gateway-specific CRDs that will allow supporting features like timeouts, load-balancing methods, authentication, etc - important data-plane features that are not part of the Gateway API spec. + +While those CRDs are not part of the Gateway API, the mechanism of attaching them to Gateway API resources resources is part of the Gateway API. See the [Policy Attachment doc](https://gateway-api.sigs.k8s.io/references/policy-attachment/). \ No newline at end of file From a1c452d4225c4d3123abaf42f2e4a9aa386f2bf2 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:47:00 -0600 Subject: [PATCH 02/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 2ff58229ca..6726a42301 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -19,7 +19,7 @@ This document describes which Gateway API resources NGINX Kubernetes Gateway sup The support status is described using the following words: - *Supported*. The resource or field is fully supported and conformant to the Gateway API specification. -- *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in the future releases. +- *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in future releases. - *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in the future releases. Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, that will be documented. From a7bfd0309bf8bd8e80544272e07494dab0baf3ed Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:47:21 -0600 Subject: [PATCH 03/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 6726a42301..83cf3dfb1b 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -20,7 +20,7 @@ This document describes which Gateway API resources NGINX Kubernetes Gateway sup The support status is described using the following words: - *Supported*. The resource or field is fully supported and conformant to the Gateway API specification. - *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in future releases. -- *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in the future releases. +- *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in future releases. Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, that will be documented. From 33914258446fe4faa7eb1663e440890f4f5ec9bb Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:47:29 -0600 Subject: [PATCH 04/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 83cf3dfb1b..c96663f8ad 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -22,7 +22,7 @@ The support status is described using the following words: - *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in future releases. - *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in future releases. -Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, that will be documented. +Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, we will document it. ## Resources From 0a8c87299c1219fb467d49a4a58d46e5fcb42b53 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:47:41 -0600 Subject: [PATCH 05/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index c96663f8ad..9db03ff99f 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -28,7 +28,7 @@ Note: it might be possible that NGINX Kubernetes Gateway will never support some Below we list the resources and the support status of their corresponding fields. -Note that we don't describe the meaning of each field. For that, please visit the [Gateway API documentation](https://gateway-api.sigs.k8s.io/references/spec/). +For a description of each field, visit the [Gateway API documentation](https://gateway-api.sigs.k8s.io/references/spec/). ### GatewayClass From 38355e2ba7a287d6c9967ecf4333abc7b8b7e596 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:49:00 -0600 Subject: [PATCH 06/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 9db03ff99f..f4ce1ee9c6 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -49,7 +49,7 @@ Fields: NGINX Kubernetes Gateway supports only a single Gateway resource: it select the Gateway resource among all resources that belong to NGINX Kubernetes Gateway (i.e. reference NGINX Kubernetes Gateway corresponding GatewayClass). In case of multiple Gateway resources, NGINX Kubernetes Gateway will use a -deterministic conflict resolution strategy: it will choose the oldest resource based on the creation timestamp. If the timestamps are equal, NGINX Kubernetes Gateway will chose the resource that appears alphabetically first based on its namespace and then name. We might support multiple Gateway resources. If you're interested in that support, please share your use case with us. +deterministic conflict resolution strategy: it will choose the oldest resource by creation timestamp. If the timestamps are equal, NGINX Kubernetes Gateway will choose the resource that appears first in alphabetical order by “{namespace}/{name}”. We might support multiple Gateway resources. Please share your use case with us if you're interested in that support. Fields: * `spec` From 06f4578f3023d34192a4fd2fb6a605513e768c52 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:49:09 -0600 Subject: [PATCH 07/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index f4ce1ee9c6..dc16813369 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -105,6 +105,6 @@ Fields: > Status: Not supported. -Custom policies will be NGINX Kubernetes Gateway-specific CRDs that will allow supporting features like timeouts, load-balancing methods, authentication, etc - important data-plane features that are not part of the Gateway API spec. +Custom policies will be NGINX Kubernetes Gateway-specific CRDs that will allow supporting features like timeouts, load-balancing methods, authentication, etc. - important data-plane features that are not part of the Gateway API spec. While those CRDs are not part of the Gateway API, the mechanism of attaching them to Gateway API resources resources is part of the Gateway API. See the [Policy Attachment doc](https://gateway-api.sigs.k8s.io/references/policy-attachment/). \ No newline at end of file From f7f00e199f7b67078d9aaef39f86dcb885556308 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:49:27 -0600 Subject: [PATCH 08/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index dc16813369..cb7e766052 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -107,4 +107,4 @@ Fields: Custom policies will be NGINX Kubernetes Gateway-specific CRDs that will allow supporting features like timeouts, load-balancing methods, authentication, etc. - important data-plane features that are not part of the Gateway API spec. -While those CRDs are not part of the Gateway API, the mechanism of attaching them to Gateway API resources resources is part of the Gateway API. See the [Policy Attachment doc](https://gateway-api.sigs.k8s.io/references/policy-attachment/). \ No newline at end of file +While those CRDs are not part of the Gateway API, the mechanism of attaching them to Gateway API resources is part of the Gateway API. See the [Policy Attachment doc](https://gateway-api.sigs.k8s.io/references/policy-attachment/). \ No newline at end of file From 39f9b5e3ae39c94a41942098c833dbae9af81027 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 11:49:38 -0600 Subject: [PATCH 09/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index cb7e766052..21d4491def 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -17,7 +17,7 @@ This document describes which Gateway API resources NGINX Kubernetes Gateway sup ## Terminology -The support status is described using the following words: +We use the following words to describe support status: - *Supported*. The resource or field is fully supported and conformant to the Gateway API specification. - *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in future releases. - *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in future releases. From 49ee7abf9e4fe25b5b779c22ee94cb717170db45 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 12:09:32 -0600 Subject: [PATCH 10/15] Add more info about status fields --- docs/gateway-api-compatibility.md.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 21d4491def..1a5605aebf 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -41,7 +41,8 @@ Fields: * `controllerName` - supported. * `parametersRef` - not supported. * `description` - supported. -* `status` - partially supported. +* `status` + * `conditions` - partially supported. ### Gateway @@ -65,7 +66,14 @@ Fields: * `options` - not supported. * `allowedRoutes` - not supported. * `addresses` - not supported. -* `status` - partially supported. +* `status` + * `addresses` - not supported. + * `conditions` - not supported. + * `listeners` + * `name` - supported. + * `supportedKinds` - not supported. + * `attachedRoutes` - supported. + * `conditions` - partially supported. ### HTTPRoute @@ -83,7 +91,11 @@ Fields: * `method` - supported. * `filters` - not supported. * `backendRefs` - partially supported. Only a single backend ref. Backend ref `filters` are not supported. NGINX Kubernetes Gateway will use the IP of the Service as a backend, not the IPs of the corresponding Pods. Watching for Service updates is not supported. -* `status` - partially supported. +* `status` + * `parents` + * `parentRef` - supported. + * `controllerName` - supported. + * `conditions` - partially supported. ### TLSRoute From a6590fdd7df5ae65e702d0ed8505ba9e3dea4113 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 12:12:24 -0600 Subject: [PATCH 11/15] Rewrite "NGINX Kubernetes Gateway supports only a single Gateway resource" --- docs/gateway-api-compatibility.md.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 1a5605aebf..445a27d8e6 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -48,9 +48,7 @@ Fields: > Status: Partially supported. -NGINX Kubernetes Gateway supports only a single Gateway resource: it select the Gateway resource among all resources that belong to -NGINX Kubernetes Gateway (i.e. reference NGINX Kubernetes Gateway corresponding GatewayClass). In case of multiple Gateway resources, NGINX Kubernetes Gateway will use a -deterministic conflict resolution strategy: it will choose the oldest resource by creation timestamp. If the timestamps are equal, NGINX Kubernetes Gateway will choose the resource that appears first in alphabetical order by “{namespace}/{name}”. We might support multiple Gateway resources. Please share your use case with us if you're interested in that support. +NGINX Kubernetes Gateway supports only a single Gateway resource. The Gateway resource must reference NGINX Kubernetes Gateway's corresponding GatewayClass. In case of multiple Gateway resources created in the cluster, NGINX Kubernetes Gateway will use a deterministic conflict resolution strategy: it will choose the oldest resource by creation timestamp. If the timestamps are equal, NGINX Kubernetes Gateway will choose the resource that appears first in alphabetical order by “{namespace}/{name}”. We might support multiple Gateway resources. Please share your use case with us if you're interested in that support. Fields: * `spec` From 7f9af179174791edf66691239508bab940db2cad Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 12:13:42 -0600 Subject: [PATCH 12/15] clarify about weight --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 445a27d8e6..5e6439d568 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -88,7 +88,7 @@ Fields: * `queryParams` - partially supported. Only `Exact` type. * `method` - supported. * `filters` - not supported. - * `backendRefs` - partially supported. Only a single backend ref. Backend ref `filters` are not supported. NGINX Kubernetes Gateway will use the IP of the Service as a backend, not the IPs of the corresponding Pods. Watching for Service updates is not supported. + * `backendRefs` - partially supported. Only a single backend ref without support for `weight`. Backend ref `filters` are not supported. NGINX Kubernetes Gateway will use the IP of the Service as a backend, not the IPs of the corresponding Pods. Watching for Service updates is not supported. * `status` * `parents` * `parentRef` - supported. From da3c2bd53c8f2fc1b82a752c04dd08ef389111f3 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 12:14:43 -0600 Subject: [PATCH 13/15] Update docs/gateway-api-compatibility.md.md Co-authored-by: kate-osborn <50597707+kate-osborn@users.noreply.github.com> --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 5e6439d568..9a2931abc5 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -60,7 +60,7 @@ Fields: * `protocol` - partially supported. Allowed values: `HTTP`, `HTTPS`. * `tls` * `mode` - partially supported. Allowed value: `Terminate`. - * `certificateRefs` - partially supported. The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls` in the same namespace as the Gateway resource. Only a single reference is supported. The Secret must be deployed before the Gateway resource. Secret rotation (watching for updates) is not supported. + * `certificateRefs` - partially supported. The TLS certificate and key must be stored in a Secret resource of type `kubernetes.io/tls` in the same namespace as the Gateway resource. Only a single reference is supported. You must deploy the Secret before the Gateway resource. Secret rotation (watching for updates) is not supported. * `options` - not supported. * `allowedRoutes` - not supported. * `addresses` - not supported. From 4406989e70bd4b5342932c44225787783d0850a2 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 14:47:31 -0600 Subject: [PATCH 14/15] Fix belows --- docs/cli-args.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cli-args.md b/docs/cli-args.md index 22ba03f9de..d308e657ef 100644 --- a/docs/cli-args.md +++ b/docs/cli-args.md @@ -1,6 +1,6 @@ # Command-line Arguments -The table belows describes the command-line arguments of the `gateway` binary from the `nginx-kubernetes-gateway` container. +The table below describes the command-line arguments of the `gateway` binary from the `nginx-kubernetes-gateway` container. | Name | Type | Description | |-|-|-| From 1f83688d8b08a60d7d5aa3b96f2c5b50b4a7d8c4 Mon Sep 17 00:00:00 2001 From: Michael Pleshakov Date: Fri, 19 Aug 2022 14:48:22 -0600 Subject: [PATCH 15/15] Rewrite --- docs/gateway-api-compatibility.md.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gateway-api-compatibility.md.md b/docs/gateway-api-compatibility.md.md index 9a2931abc5..66ef575b96 100644 --- a/docs/gateway-api-compatibility.md.md +++ b/docs/gateway-api-compatibility.md.md @@ -22,7 +22,7 @@ We use the following words to describe support status: - *Partially supported*. The resource or field is supported partially or with limitations. It will become fully supported in future releases. - *Not supported*. The resource or field is not yet supported. It will become partially or fully supported in future releases. -Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. If that happens, we will document it. +Note: it might be possible that NGINX Kubernetes Gateway will never support some resources and/or fields of the Gateway API. We will document these decisions on a case by case basis. ## Resources