Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DO NOT MERGE] Test upgrade gateway API to v1.0.0-rc2 #1169

Closed
wants to merge 6 commits into from
Closed

[DO NOT MERGE] Test upgrade gateway API to v1.0.0-rc2 #1169

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
fb8890c
Test gw API v1.0.0-rc1
ciarams87 Oct 20, 2023
7d2c68e
Update CRDs in helm CI step
ciarams87 Oct 20, 2023
92258ff
Update to use rc2
ciarams87 Oct 26, 2023
a7f1874
Update docs & fix makefile
ciarams87 Oct 26, 2023
1ce10fc
Test failing conformance tests in pipeline
ciarams87 Oct 26, 2023
9077476
Test pipeline again
ciarams87 Oct 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,8 +222,7 @@ jobs:
make create-kind-cluster KIND_KUBE_CONFIG=${kube_config}
echo "KUBECONFIG=${kube_config}" >> "$GITHUB_ENV"
kind load docker-image ${{ steps.ngf-meta.outputs.tags }} ${{ steps.nginx-meta.outputs.tags }}
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.8.1/standard-install.yaml
kubectl wait --for=condition=complete job/gateway-api-admission-patch job/gateway-api-admission -n gateway-system
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0-rc1/standard-install.yaml

- name: Install Chart
run: >
Expand Down
6 changes: 5 additions & 1 deletion .github/workflows/conformance.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,11 @@ jobs:
working-directory: ./conformance

- name: Run conformance tests
run: make run-conformance-tests TAG=${{ github.sha }} VERSION=${{ github.ref_name }}
run: |
make run-conformance-tests TAG=${{ github.sha }} VERSION=${{ github.ref_name }}
core_result=$(cat conformance-profile.yaml | yq '.profiles[0].core.result')
extended_result=$(cat conformance-profile.yaml | yq '.profiles[0].extended.result')
if [ "${core_result}" == "failure" ] || [ "${extended_result}" == "failure" ]; then echo "Conformance test failed, see previous job for details." && exit 2; fi
working-directory: ./conformance

- name: Upload profile to release
Expand Down
8 changes: 3 additions & 5 deletions conformance/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
NGF_TAG = edge
NGF_PREFIX = nginx-gateway-fabric
NGINX_IMAGE_NAME = $(NGF_PREFIX)/nginx
GW_API_VERSION ?= 0.8.1
GW_API_VERSION ?= 1.0.0-rc2
GATEWAY_CLASS = nginx
SUPPORTED_FEATURES = HTTPRoute,HTTPRouteQueryParamMatching,HTTPRouteMethodMatching,HTTPRoutePortRedirect,HTTPRouteSchemeRedirect,GatewayClassObservedGenerationBump
KIND_IMAGE ?= $(shell grep -m1 'FROM kindest/node' <tests/Dockerfile | awk -F'[ ]' '{print $$2}')
Expand Down Expand Up @@ -48,7 +48,6 @@ load-images: ## Load NGF and NGINX images on configured kind cluster
.PHONY: prepare-ngf-dependencies
prepare-ngf-dependencies: update-ngf-manifest ## Install NGF dependencies on configured kind cluster
./scripts/install-gateway.sh $(GW_API_VERSION)
kubectl wait --for=condition=available --timeout=60s deployment gateway-api-admission-server -n gateway-system
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the reason for removing wait here and in ci.yaml?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was a quick fix for testing purposes - they removed default installation of Gateway API admission server and related resources (because of the move to using CEL validation instead). We'll actually want to update to optionally install these resources for cases where the k8s version is <1.26. See kubernetes-sigs/gateway-api#2400

kubectl apply -f $(CRDS)
kubectl apply -f $(NGF_MANIFEST)

Expand Down Expand Up @@ -79,9 +78,8 @@ run-conformance-tests: ## Run conformance tests
--report-output=output.txt; cat output.txt" | tee output.txt
sed -e '1,/CONFORMANCE PROFILE/d' output.txt > conformance-profile.yaml
rm output.txt
$(eval result_core=$(shell cat conformance-profile.yaml | yq '.profiles[0].core.result'))
$(eval result_extended=$(shell cat conformance-profile.yaml | yq '.profiles[0].extended.result'))
[ "$(result_core)" != "failure" ] && [ "$(result_extended)" != "failure" ] || exit 2
[ $(shell cat conformance-profile.yaml | yq '.profiles[0].core.result') != "failure" ] \
&& [ $(shell cat conformance-profile.yaml | yq '.profiles[0].extended.result') != "failure" ] || exit 2

.PHONY: cleanup-conformance-tests
cleanup-conformance-tests: ## Clean up conformance tests fixtures
Expand Down
1 change: 0 additions & 1 deletion conformance/scripts/install-gateway.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ if [ $1 == "main" ]; then
temp_dir=$(mktemp -d)
cd ${temp_dir}
curl -s https://codeload.github.com/kubernetes-sigs/gateway-api/tar.gz/main | tar -xz --strip=2 gateway-api-main/config
kubectl apply -f webhook
kubectl apply -f crd/standard
rm -rf ${temp_dir}
else
Expand Down
1 change: 0 additions & 1 deletion conformance/scripts/uninstall-gateway.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ if [ $1 == "main" ]; then
temp_dir=$(mktemp -d)
cd ${temp_dir}
curl -s https://codeload.github.com/kubernetes-sigs/gateway-api/tar.gz/main | tar -xz --strip=2 gateway-api-main/config
kubectl delete -f webhook
kubectl delete -f crd/standard
rm -rf ${temp_dir}
else
Expand Down
2 changes: 2 additions & 0 deletions conformance/tests/conformance_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ import (
"k8s.io/apimachinery/pkg/util/sets"
"sigs.k8s.io/controller-runtime/pkg/client"
"sigs.k8s.io/controller-runtime/pkg/client/config"
"sigs.k8s.io/gateway-api/apis/v1"
"sigs.k8s.io/gateway-api/apis/v1alpha2"
"sigs.k8s.io/gateway-api/apis/v1beta1"
"sigs.k8s.io/gateway-api/conformance/apis/v1alpha1"
Expand All @@ -43,6 +44,7 @@ func TestConformance(t *testing.T) {
g.Expect(err).To(BeNil())

g.Expect(v1alpha2.AddToScheme(client.Scheme())).To(Succeed())
g.Expect(v1.AddToScheme(client.Scheme())).To(Succeed())
g.Expect(v1beta1.AddToScheme(client.Scheme())).To(Succeed())

supportedFeatures := suite.ParseSupportedFeatures(*flags.SupportedFeatures)
Expand Down
2 changes: 1 addition & 1 deletion deploy/helm-chart/templates/gatewayclass.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
name: {{ .Values.nginxGateway.gatewayClassName }}
Expand Down
2 changes: 1 addition & 1 deletion deploy/manifests/nginx-gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ spec:
emptyDir: {}
---
# Source: nginx-gateway-fabric/templates/gatewayclass.yaml
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
name: nginx
Expand Down
2 changes: 1 addition & 1 deletion design/resource-validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ We will introduce two validation methods to be run by NGF control plane:
### Re-run of Webhook Validation

Before processing a resource, NGF will validate it using the functions from
the [validation package](https://github.com/kubernetes-sigs/gateway-api/tree/b241afc88e68c952cc0a59a5c72a51358dc2bada/apis/v1beta1/validation)
the [validation package](https://github.com/kubernetes-sigs/gateway-api/tree/fa4b0a519b30a33b205ac0256876afc1456f2dd3/apis/v1/validation)
from the Gateway API. This will ensure that the webhook validation cannot be bypassed (it can be bypassed if the webhook
is not installed, misconfigured, or running a different version), and it will allow us to avoid repeating the same
validation in our code.
Expand Down
6 changes: 3 additions & 3 deletions docs/developer/logging-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,15 +188,15 @@ The next section shows how to add context.

```go
// hr implements client.Object (controller-runtime)
// hr is *v1beta1.HTTPRoute
// hr is *v1.HTTPRoute
logger.Info(
"Processed resource",
"resource", hr,
)
```

```json
{"level":"info","ts":"2023-07-20T15:10:03-04:00","msg":"Processed resource","resource":{"apiVersion":"gateway.networking.k8s.io/v1beta1","kind":"HTTPRoute","namespace":"test","name":"hr-1"}}
{"level":"info","ts":"2023-07-20T15:10:03-04:00","msg":"Processed resource","resource":{"apiVersion":"gateway.networking.k8s.io/v1","kind":"HTTPRoute","namespace":"test","name":"hr-1"}}
```

> The resource must include `TypeMeta`, otherwise its `apiVersion` and `kind` will not be printed.
Expand Down Expand Up @@ -276,7 +276,7 @@ For the developer, log messages are formatted as text strings (except key/values
example:

```text
2023-07-21T12:41:37.640-0400 INFO Processed resource {"resource": {"apiVersion": "gateway.networking.k8s.io/v1beta1", "kind": "HTTPRoute", "namespace": "test", "name": "hr-1"}}
2023-07-21T12:41:37.640-0400 INFO Processed resource {"resource": {"apiVersion": "gateway.networking.k8s.io/v1", "kind": "HTTPRoute", "namespace": "test", "name": "hr-1"}}
```

The formatting is controlled during the logger initialization.
Expand Down
6 changes: 3 additions & 3 deletions docs/gateway-api-compatibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ This document describes which Gateway API resources NGINX Gateway Fabric support

| Resource | Core Support Level | Extended Support Level | Implementation-Specific Support Level | API Version |
|-------------------------------------|--------------------|------------------------|---------------------------------------|-------------|
| [GatewayClass](#gatewayclass) | Supported | Not supported | Not Supported | v1beta1 |
| [Gateway](#gateway) | Supported | Not supported | Not Supported | v1beta1 |
| [HTTPRoute](#httproute) | Supported | Partially supported | Not Supported | v1beta1 |
| [GatewayClass](#gatewayclass) | Supported | Not supported | Not Supported | v1 |
| [Gateway](#gateway) | Supported | Not supported | Not Supported | v1 |
| [HTTPRoute](#httproute) | Supported | Partially supported | Not Supported | v1 |
| [ReferenceGrant](#referencegrant) | Supported | N/A | Not Supported | v1beta1 |
kate-osborn marked this conversation as resolved.
Show resolved Hide resolved
| [Custom policies](#custom-policies) | Not supported | N/A | Not Supported | N/A |
| [TLSRoute](#tlsroute) | Not supported | Not supported | Not Supported | N/A |
Expand Down
6 changes: 3 additions & 3 deletions docs/guides/advanced-routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ The [Gateway](https://gateway-api.sigs.k8s.io/api-types/gateway/) resource is ty

```yaml
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: cafe
Expand All @@ -66,7 +66,7 @@ The [HTTPRoute](https://gateway-api.sigs.k8s.io/api-types/httproute/) is typical

```yaml
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand Down Expand Up @@ -175,7 +175,7 @@ We are reusing the previous Gateway for these applications, so all we need to cr

```yaml
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: tea
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/integrating-cert-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Next we need to deploy our Gateway. Use can use the below YAML manifest, updatin
field to the required value for your environment.

```yaml
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: gateway
Expand Down Expand Up @@ -216,7 +216,7 @@ Deploy our HTTPRoute to configure our routing rules for the coffee application.
spec refers to the Listener configured in the previous step.

```yaml
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand Down
18 changes: 9 additions & 9 deletions docs/guides/routing-traffic-to-your-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ With this architecture, the coffee application is not accessible outside the clu
on the hostname `cafe.example.com` so that clients outside the cluster can access it.

To do this, we will install NGINX Gateway Fabric and create two Gateway API resources:
a [Gateway](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.Gateway) and
an [HTTPRoute](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRoute).
a [Gateway](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Gateway) and
an [HTTPRoute](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRoute).
With these resources, we will configure a simple routing rule to match all HTTP traffic with the
hostname `cafe.example.com` and route it to the coffee Service.

Expand Down Expand Up @@ -124,7 +124,7 @@ To create the `cafe` Gateway, copy and paste the following into your terminal:

```yaml
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: cafe
Expand All @@ -143,20 +143,20 @@ only configure Gateways with a `gatewayClassName` of `nginx` unless you change t
[command-line flag](/docs/cli-help.md#static-mode).

We specify
a [listener](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.Listener) on
a [Listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Listener) on
the Gateway to open an entry point on the cluster. In this case, since the coffee application accepts HTTP requests, we
create an HTTP listener, named `http`, that listens on port 80.

By default, Gateways only allow routes (such as HTTPRoutes) to attach if they are in the same namespace as the Gateway.
If you want to change this behavior, you can set
the [`allowedRoutes`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.AllowedRoutes)
the [`allowedRoutes`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.AllowedRoutes)
field.

Now, let's create the HTTPRoute by copying and pasting the following into your terminal:

```yaml
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand All @@ -177,16 +177,16 @@ EOF
```

To attach the `coffee` HTTPRoute to the `cafe` Gateway, we specify the Gateway name in
the [`parentRefs`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.CommonRouteSpec)
the [`parentRefs`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.CommonRouteSpec)
field. The attachment will succeed if the hostnames and protocol in the HTTPRoute are allowed by at least one of the
Gateway's listeners.

The [`hostnames`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteSpec)
The [`hostnames`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRouteSpec)
field allows you to list the hostnames that the HTTPRoute matches. In this case, incoming requests handled by the `http`
listener with the HTTP host header `cafe.example.com` will match this HTTPRoute and will be routed according to the
rules in the spec.

The [`rules`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRouteRule)
The [`rules`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule)
field defines routing rules for the HTTPRoute. A rule is selected if the request satisfies one of the rule's `matches`.
To forward traffic for all paths to the coffee Service we specify a match with the PathPrefix `/` and target the coffee
Service using the `backendRef` field.
Expand Down
2 changes: 1 addition & 1 deletion docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ the `--service` argument to the controller.

> **Important**
> The Service manifests expose NGINX Gateway Fabric on ports 80 and 443, which exposes any
> Gateway [Listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.Listener)
> Gateway [Listener](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Listener)
> configured for those ports. If you'd like to use different ports in your listeners,
> update the manifests accordingly.
>
Expand Down
4 changes: 2 additions & 2 deletions examples/advanced-routing/cafe-routes.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand Down Expand Up @@ -32,7 +32,7 @@ spec:
- name: coffee-v2-svc
port: 80
---
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: tea
Expand Down
2 changes: 1 addition & 1 deletion examples/advanced-routing/gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: cafe
Expand Down
4 changes: 2 additions & 2 deletions examples/cafe-example/cafe-routes.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand All @@ -17,7 +17,7 @@ spec:
- name: coffee
port: 80
---
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: tea
Expand Down
2 changes: 1 addition & 1 deletion examples/cafe-example/gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: gateway
Expand Down
4 changes: 2 additions & 2 deletions examples/cross-namespace-routing/cafe-routes.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand All @@ -18,7 +18,7 @@ spec:
namespace: cafe
port: 80
---
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: tea
Expand Down
2 changes: 1 addition & 1 deletion examples/cross-namespace-routing/gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: gateway
Expand Down
2 changes: 1 addition & 1 deletion examples/http-header-filter/echo-route.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: headers
Expand Down
2 changes: 1 addition & 1 deletion examples/http-header-filter/gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: gateway
Expand Down
4 changes: 2 additions & 2 deletions examples/https-termination/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ reference a Secret in a different Namespace.

To configure HTTPS termination for our cafe application, we will bind our `coffee` and `tea` HTTPRoutes to
the `https` listener in [cafe-routes.yaml](./cafe-routes.yaml) using
the [`parentReference`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ParentReference)
the [`parentReference`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.ParentReference)
field:

```yaml
Expand All @@ -91,7 +91,7 @@ reference a Secret in a different Namespace.
```

To configure an HTTPS redirect from port 80 to 443, we will bind the special `cafe-tls-redirect` HTTPRoute with
a [`HTTPRequestRedirectFilter`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRequestRedirectFilter)
a [`HTTPRequestRedirectFilter`](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRequestRedirectFilter)
to the `http` listener:

```yaml
Expand Down
6 changes: 3 additions & 3 deletions examples/https-termination/cafe-routes.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: cafe-tls-redirect
Expand All @@ -15,7 +15,7 @@ spec:
scheme: https
port: 443
---
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: coffee
Expand All @@ -34,7 +34,7 @@ spec:
- name: coffee
port: 80
---
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: tea
Expand Down
2 changes: 1 addition & 1 deletion examples/https-termination/gateway.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: gateway
Expand Down
2 changes: 1 addition & 1 deletion examples/traffic-splitting/cafe-route-equal-weight.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
apiVersion: gateway.networking.k8s.io/v1beta1
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: cafe-route
Expand Down
Loading
Loading