[release/v1.0]: release v1.0.1 (#3149)

.github/workflows/docs.yaml

@@ -31,6 +31,13 @@ jobs:
         files: site/content/*
         config_file: ".github/markdown_lint_config.json"
 
+    - name: Install linkinator
+      run: npm install -g [email protected]
+
+    - name: Check links
+      run: make docs docs-check-links
+      continue-on-error: true
+
   docs-build:
     runs-on: ubuntu-latest
     needs: docs-lint

VERSION

@@ -1 +1 @@
-v1.0.0
+v1.0.1

release-notes/v1.0.1.yaml

@@ -0,0 +1,25 @@
+date: April 9, 2024
+
+changes:
+  - area: installation
+    change: |
+      Updated EnvoyProxy version to v1.29.3
+      Fixed certgen to support creating the hmac secret during an upgrade
+
+  - area: translator
+    change: |
+      Fixed nil secret in resourceversiontable
+      Add missing http filters to the http filter chain when ClientTrafficPolicy and MergeGateways is enabled
+      Allow websockets when url rewrite is enabled
+      Set the Host header for http health checker
+      Fixed double slashes in redirect URL
+      Allow ClientTrafficPolicy to attach to multiple http (non https) listeners within the same Gateway
+      Set path prefix for the http ext auth service
+      Set the route matching precedence order to Exact > RegularExpression > PathPrefix
+      Fixed infraIR duplicate port translation for merged gateways
+      Set SpawnUpstreamSpan to true
+      Allow rate limit to work with multiple listeners
+
+  - area: infra-manager
+    change: |
+      Skip creating infra resources when the InfraIR has empty listeners

site/content/en/_index.md

@@ -3,10 +3,10 @@ title: Envoy Gateway
 ---
 
 {{< blocks/cover title="Welcome to Envoy Gateway!" image_anchor="top" height="full" >}}
-<a class="btn btn-lg btn-primary me-3 mb-4" href="/v1.0.0">
+<a class="btn btn-lg btn-primary me-3 mb-4" href="/v1.0.1">
   GET STARTED <i class="fas fa-arrow-alt-circle-right ms-2"></i>
 </a>
-<a class="btn btn-lg btn-secondary me-3 mb-4" href="/v1.0.0/contributions">
+<a class="btn btn-lg btn-secondary me-3 mb-4" href="/v1.0.1/contributions">
   CONTRIBUTING <i class="fa fa-heartbeat ms-2 "></i>
 </a>
 <p class="lead mt-5">Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway</p>

site/content/en/latest/releases/v1.0.1.md

@@ -0,0 +1,27 @@
+---
+title: "v1.0.1"
+publishdate: 2024-04-09
+---
+
+Date: April 9, 2024
+
+## Installation
+- Updated EnvoyProxy version to v1.29.3
+- Fixed certgen to support creating the hmac secret during an upgrade
+
+## Translator
+- Fixed nil secret in resourceversiontable
+- Add missing http filters to the http filter chain when ClientTrafficPolicy and MergeGateways is enabled
+- Allow websockets when url rewrite is enabled
+- Set the Host header for http health checker
+- Fixed double slashes in redirect URL
+- Allow ClientTrafficPolicy to attach to multiple http (non https) listeners within the same Gateway
+- Set path prefix for the http ext auth service
+- Set the route matching precedence order to Exact > RegularExpression > PathPrefix
+- Fixed infraIR duplicate port translation for merged gateways
+- Set SpawnUpstreamSpan to true
+- Allow rate limit to work with multiple listeners
+
+## Infra-manager
+- Skip creating infra resources when the InfraIR has empty listeners
+

site/content/en/v1.0.0/install/install-helm.md → site/content/en/v1.0.1/install/install-helm.md

@@ -18,7 +18,7 @@ The Envoy Gateway Helm chart is hosted by DockerHub.
 It is published at `oci://docker.io/envoyproxy/gateway-helm`.
 
 {{% alert title="Note" color="primary" %}}
-We use `v0.0.0-latest` as the latest development version.
+We use `v1.0.1` as the latest development version.
 
 You can visit [Envoy Gateway Helm Chart](https://hub.docker.com/r/envoyproxy/gateway-helm/tags) for more releases.
 {{% /alert %}}
@@ -34,7 +34,7 @@ Refer to the [Developer Guide](/latest/contributions/develop) to learn more.
 Install the Gateway API CRDs and Envoy Gateway:
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system --create-namespace
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace
 ```
 
 Wait for Envoy Gateway to become available:
@@ -66,15 +66,15 @@ Some of the quick ways of using the helm install command for envoy gateway insta
 ### Increase the replicas
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system --create-namespace --set deployment.replicas=2
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace --set deployment.replicas=2
 ```
 
 ### Change the kubernetesClusterDomain name
 
 If you have installed your cluster with different domain name you can use below command.
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system --create-namespace --set kubernetesClusterDomain=<domain name>
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace --set kubernetesClusterDomain=<domain name>
 ```
 
 **Note**: Above are some of the ways we can directly use for customization of our installation. But if you are looking for more complex changes [values.yaml](https://helm.sh/docs/chart_template_guide/values_files/) comes to rescue.
@@ -111,7 +111,7 @@ Here we have made three changes to our values.yaml file. Increase the resources
 You can use the below command to install the envoy gateway using values.yaml file.
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system --create-namespace -f values.yaml
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace -f values.yaml
 ```
 
 {{% alert title="Helm Chart Values" color="primary" %}}

site/content/en/v1.0.0/user/operations/deployment-mode.md → site/content/en/v1.0.1/user/operations/deployment-mode.md

@@ -50,7 +50,7 @@ helm install \
 --set config.envoyGateway.provider.kubernetes.watch.type=Namespaces \
 --set config.envoyGateway.provider.kubernetes.watch.namespaces={marketing} \
 eg-marketing oci://docker.io/envoyproxy/gateway-helm \
---version v0.0.0-latest -n marketing --create-namespace
+--version v1.0.1 -n marketing --create-namespace
 ```
 
 Lets create a `GatewayClass` linked to the marketing team's Envoy Gateway controller, and as well other resources linked to it, so the `backend` application operated by this team can be exposed to external clients.
@@ -228,7 +228,7 @@ helm install \
 --set config.envoyGateway.provider.kubernetes.watch.type=Namespaces \
 --set config.envoyGateway.provider.kubernetes.watch.namespaces={product} \
 eg-product oci://docker.io/envoyproxy/gateway-helm \
---version v0.0.0-latest -n product --create-namespace
+--version v1.0.1 -n product --create-namespace
 ```
 
 Lets create a `GatewayClass` linked to the product team's Envoy Gateway controller, and as well other resources linked to it, so the `backend` application operated by this team can be exposed to external clients.

site/content/en/v1.0.0/user/quickstart.md → site/content/en/v1.0.1/user/quickstart.md

@@ -20,7 +20,7 @@ so the `Gateway` resource has an Address associated with it. We recommend using
 Install the Gateway API CRDs and Envoy Gateway:
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.0 -n envoy-gateway-system --create-namespace
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace
 ```
 
 Wait for Envoy Gateway to become available:
@@ -32,7 +32,7 @@ kubectl wait --timeout=5m -n envoy-gateway-system deployment/envoy-gateway --for
 Install the GatewayClass, Gateway, HTTPRoute and example app:
 
 ```shell
-kubectl apply -f https://github.com/envoyproxy/gateway/releases/download/v1.0.0/quickstart.yaml -n default
+kubectl apply -f https://github.com/envoyproxy/gateway/releases/download/v1.0.1/quickstart.yaml -n default
 ```
 
 **Note**: [`quickstart.yaml`] defines that Envoy Gateway will listen for
@@ -43,7 +43,7 @@ unprivileged port, so that Envoy Gateway doesn't need additional privileges.
 It's important to be aware of this mapping, since you may need to take it into
 consideration when debugging.
 
-[`quickstart.yaml`]: https://github.com/envoyproxy/gateway/releases/download/v1.0.0/quickstart.yaml
+[`quickstart.yaml`]: https://github.com/envoyproxy/gateway/releases/download/v1.0.1/quickstart.yaml
 
 ## Testing the Configuration
 
@@ -90,7 +90,7 @@ Use the steps in this section to uninstall everything from the quickstart guide.
 Delete the GatewayClass, Gateway, HTTPRoute and Example App:
 
 ```shell
-kubectl delete -f https://github.com/envoyproxy/gateway/releases/download/v1.0.0/quickstart.yaml --ignore-not-found=true
+kubectl delete -f https://github.com/envoyproxy/gateway/releases/download/v1.0.1/quickstart.yaml --ignore-not-found=true
 ```
 
 Delete the Gateway API CRDs and Envoy Gateway: