release: v1.0.2 (#3594)

* release: v1.0.2

Signed-off-by: bitliu <bitliu@tencent.com>

* resolve feedbacks

Signed-off-by: bitliu <bitliu@tencent.com>

* resolve feedbacks

Signed-off-by: bitliu <bitliu@tencent.com>

---------

Signed-off-by: bitliu <bitliu@tencent.com>

VERSION

@@ -1 +1 @@
-v1.0.1
+v1.0.2

release-notes/v1.0.2.yaml

@@ -0,0 +1,28 @@
+date: June 12, 2024
+
+changes:
+  - area: installation
+    change: |
+      Updated EnvoyProxy to 1.29.5
+      Use Patch API for infra-client
+      Use ServerSideApply instead of CreateOrUpdate for infra-client
+
+  - area: testing
+    change: |
+      Fixed failures due to an expired certificate in one of the translator tests
+
+  - area: translator
+    change: |
+      Use <proto>-<port> for naming service and container ports
+      Added proxy protocol always as first listenerFilter
+      Set ignoreCase for header matchers in extAuth
+      Added backend TLS SAN validation
+      Fixed ReplaceFullPath not working for root path (/)
+
+  - area: providers
+    change: |
+      Fixed duplicated xroutes are added to gatewayapi Resources
+      Fixed security policy reference grant from field type
+      Fixed Route extension filters with different types but the same name and namespace aren't correctly cached
+      Fixed secrets/configmap updates to trigger a controller reconcile by removing the generationChanged predicate
+      Removed namespace restriction for EnvoyProxy parametersRef

site/content/en/_index.md

@@ -3,7 +3,7 @@ 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.1">
+<a class="btn btn-lg btn-primary me-3 mb-4" href="/v1.0.2">
   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="/contributions">

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

@@ -0,0 +1,29 @@
+---
+title: "v1.0.2"
+publishdate: 2024-06-12
+---
+
+Date: June 12, 2024
+
+## Installation
+- Updated EnvoyProxy to 1.29.5
+- Use Patch API for infra-client
+- Use ServerSideApply instead of CreateOrUpdate for infra-client
+
+## Testing
+- Fixed failures due to an expired certificate in one of the translator tests
+
+## Translator
+- Use <proto>-<port> for naming service and container ports
+- Added proxy protocol always as first listenerFilter
+- Set ignoreCase for header matchers in extAuth
+- Added backend TLS SAN validation
+- Fixed ReplaceFullPath not working for root path (/)
+
+## Providers
+- Fixed duplicated xroutes are added to gatewayapi Resources
+- Fixed security policy reference grant from field type
+- Fixed Route extension filters with different types but the same name and namespace aren't correctly cached
+- Fixed secrets/configmap updates to trigger a controller reconcile by removing the generationChanged predicate
+- Removed namespace restriction for EnvoyProxy parametersRef
+

site/content/en/news/blogs/1.0-release/1.0-release.md

@@ -12,19 +12,19 @@ Today we’re ecstatic to announce the 1.0 release of Envoy Gateway (EG) for Kub
 After nearly two years with contributions from over 90 engineers we are proud to say EG meets the goals that Matt outlined in the [original post](https://blog.envoyproxy.io/introducing-envoy-gateway-ad385cc59532) introducing the project, summarized here:
 * Built around the (then emerging) [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io)
 * Addresses common needs with a solution that is simple to configure and understand
-* Provides [great docs](/v1.0.1/tasks/) for common use cases to enable ease of adoption
+* Provides [great docs](/v1.0.2/tasks/) for common use cases to enable ease of adoption
 * Empowers the community and vendors to drive the project forward through an extensible API
 
-Can’t wait to try it? Visit the EG [tasks](/v1.0.1/tasks/) to get started with Envoy Gateway 1.0
+Can’t wait to try it? Visit the EG [tasks](/v1.0.2/tasks/) to get started with Envoy Gateway 1.0
 
 ## Envoy Gateway 1.0
 
 The 1.0 release brings a lot of functionality. In addition to implementing the full Kubernetes Gateway API – including the awesome Envoy L7 features you love like per-request policy, load balancing, and best-in-class observability – it also goes further, Envoy Gateway 1.0:
 * Provides support for common features such as Rate Limiting and OAuth2.0
 * Deploys and upgrades Envoy on your behalf, easing operations and lifecycle management
-* Introduces extensions to the Kubernetes Gateway API to address [Client](/v1.0.1/api/extension_types#clienttrafficpolicy), [Backend](/v1.0.1/api/extension_types#backendtrafficpolicy), and [Security](/v1.0.1/api/extension_types#securitypolicy) settings and features
-* Is easily extensible through the [EnvoyPatchPolicy](/v1.0.1/tasks/extensibility/envoy-patch-policy/) API to allow you to configure any Envoy behavior (including stuff you build yourself!)
-* Has a CLI, [egctl](/v1.0.1/tasks/operations/egctl/), for interacting with and debugging the system
+* Introduces extensions to the Kubernetes Gateway API to address [Client](/v1.0.2/api/extension_types#clienttrafficpolicy), [Backend](/v1.0.2/api/extension_types#backendtrafficpolicy), and [Security](/v1.0.2/api/extension_types#securitypolicy) settings and features
+* Is easily extensible through the [EnvoyPatchPolicy](/v1.0.2/tasks/extensibility/envoy-patch-policy/) API to allow you to configure any Envoy behavior (including stuff you build yourself!)
+* Has a CLI, [egctl](/v1.0.2/tasks/operations/egctl/), for interacting with and debugging the system
 * Comes with a large (and growing!) set of scenarios to make common use cases straightforward to implement
 
 ## What Does 1.0 Mean for the Project?
@@ -59,7 +59,7 @@ Following the 1.0 release, we’ll be focusing on:
 * **Scale**: Building out a performance benchmarking tool into our CI
 * **Extensibility**: We plan on providing a first-class API for data plane extensions such as Lua, WASM, and Ext Proc to enable users to implement their custom use cases
 * **Outside of Kubernetes**: Running Envoy Gateway in non-k8s environments - this has been an [explicit goal](/contributions/design/goals#all-environments) and we’d like to focus on this in the coming months. Envoy Proxy already supports running on bare metal environments, with Envoy Gateway users getting the added advantage of a simpler API
-* **Debug**: And a lot of capabilities with the [egctl CLI](/v1.0.1/tasks/operations/egctl/)
+* **Debug**: And a lot of capabilities with the [egctl CLI](/v1.0.2/tasks/operations/egctl/)
 
 ## Get Started
-If you’ve been looking to use Envoy as a Gateway, check out our [quickstart guide](/v1.0.1/tasks/quickstart) and give it a try! If you’re interested in contributing, check out our [guide for getting involved](/contributions/)!
+If you’ve been looking to use Envoy as a Gateway, check out our [quickstart guide](/v1.0.2/tasks/quickstart) and give it a try! If you’re interested in contributing, check out our [guide for getting involved](/contributions/)!

site/content/en/news/releases/v1.0.md

@@ -195,6 +195,6 @@ The release adds a ton of features and functionality. Here are some highlights:
 - Added Support for egctl translate from gateway-api resources to IR
 
 [Release Notes]: https://github.com/envoyproxy/gateway/blob/main/release-notes/v1.0.0.yaml
-[matrix]: /v1.0.1/install/matrix/
-[docs]: /v1.0.1/
+[matrix]: /v1.0.2/install/matrix/
+[docs]: /v1.0.2/
 [Download]: https://github.com/envoyproxy/gateway/releases/tag/v1.0.0

site/content/en/v1.0.1/install/install-helm.md → site/content/en/v1.0.2/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 `v1.0.1` as the latest development version.
+We use `v1.0.2` 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](../../contributions/develop) to learn more.
 Install the Gateway API CRDs and Envoy Gateway:
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -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 v1.0.1 -n envoy-gateway-system --create-namespace --set deployment.replicas=2
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -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 v1.0.1 -n envoy-gateway-system --create-namespace --set kubernetesClusterDomain=<domain name>
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -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 v1.0.1 -n envoy-gateway-system --create-namespace -f values.yaml
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -n envoy-gateway-system --create-namespace -f values.yaml
 ```
 
 {{% alert title="Helm Chart Values" color="primary" %}}

site/content/en/v1.0.1/install/install-yaml.md → site/content/en/v1.0.2/install/install-yaml.md

@@ -31,7 +31,7 @@ Refer to the [Developer Guide](../../contributions/develop) to learn more.
 1. In your terminal, run the following command:
 
     ```shell
-    kubectl apply --server-side -f https://github.com/envoyproxy/gateway/releases/download/v1.0.1/install.yaml
+    kubectl apply --server-side -f https://github.com/envoyproxy/gateway/releases/download/v1.0.2/install.yaml
     ```
 
 2. Next Steps

site/content/en/v1.0.2/releases/v1.0.2.md

@@ -0,0 +1,28 @@
+---
+title: "v1.0.2"
+publishdate: 2024-06-12
+---
+
+Date: June 12, 2024
+
+## Installation
+- Use Patch API for infra-client
+- Use ServerSideApply instead of CreateOrUpdate for infra-client
+
+## Testing
+- Fixed failures due to an expired certificate in one of the translator tests
+
+## Translator
+- Use <proto>-<port> for naming service and container ports
+- Added proxy protocol always as first listenerFilter
+- Set ignoreCase for header matchers in extAuth
+- Added backend TLS SAN validation
+- Fixed ReplaceFullPath not working for root path (/)
+
+## Providers
+- Fixed duplicated xroutes are added to gatewayapi Resources
+- Fixed security policy reference grant from field type
+- Fixed Route extension filters with different types but the same name and namespace aren't correctly cached
+- Fixed secrets/configmap updates do not trigger a controller reconcile
+- Removed namespace restriction for EnvoyProxy parametersRef
+

site/content/en/v1.0.1/tasks/operations/deployment-mode.md → site/content/en/v1.0.2/tasks/operations/deployment-mode.md

@@ -52,7 +52,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 v1.0.1 -n marketing --create-namespace
+--version v1.0.2 -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.
@@ -230,7 +230,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 v1.0.1 -n product --create-namespace
+--version v1.0.2 -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.1/tasks/quickstart.md → site/content/en/v1.0.2/tasks/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.1 -n envoy-gateway-system --create-namespace
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -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.1/quickstart.yaml -n default
+kubectl apply -f https://github.com/envoyproxy/gateway/releases/download/v1.0.2/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.1/quickstart.yaml
+[`quickstart.yaml`]: https://github.com/envoyproxy/gateway/releases/download/v1.0.2/quickstart.yaml
 
 ## Testing the Configuration
 
@@ -107,7 +107,7 @@ Use the steps in this section to uninstall everything from the quickstart.
 Delete the GatewayClass, Gateway, HTTPRoute and Example App:
 
 ```shell
-kubectl delete -f https://github.com/envoyproxy/gateway/releases/download/v1.0.1/quickstart.yaml --ignore-not-found=true
+kubectl delete -f https://github.com/envoyproxy/gateway/releases/download/v1.0.2/quickstart.yaml --ignore-not-found=true
 ```
 
 Delete the Gateway API CRDs and Envoy Gateway:

site/content/en/v1.0.1/tasks/traffic/multicluster-service.md → site/content/en/v1.0.2/tasks/traffic/multicluster-service.md

@@ -39,7 +39,7 @@ Once the above steps are done and all the pods are up in both the clusters. We a
 Install the Gateway API CRDs and Envoy Gateway in cluster1:
 
 ```shell
-helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.1 -n envoy-gateway-system --create-namespace --kubeconfig output/kubeconfigs/kind-config-cluster1
+helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.0.2 -n envoy-gateway-system --create-namespace --kubeconfig output/kubeconfigs/kind-config-cluster1
 ```
 
 Wait for Envoy Gateway to become available:

site/content/zh/_index.md

@@ -3,7 +3,7 @@ title: Envoy Gateway
 ---
 
 {{< blocks/cover title="欢迎访问 Envoy Gateway！" image_anchor="top" height="full" >}}
-<a class="btn btn-lg btn-primary me-3 mb-4" href="/v1.0.1">
+<a class="btn btn-lg btn-primary me-3 mb-4" href="/v1.0.2">
   开始使用 <i class="fas fa-arrow-alt-circle-right ms-2"></i>
 </a>
 <a class="btn btn-lg btn-secondary me-3 mb-4" href="/contributions">

site/hugo.toml

@@ -253,7 +253,7 @@ enable = true
   [[menu.main]]
     name = "Documentation"
     weight = -102
-    url = "/v1.0.1"
+    url = "/v1.0.2"
 
   # i18n for Chinese
   [[languages.zh.menu.main]]
@@ -278,8 +278,8 @@ enable = true
   url = "/latest"
 
 [[params.versions]]
-  version = "v1.0.1"
-  url = "/v1.0.1"
+  version = "v1.0.2"
+  url = "/v1.0.2"
 
 [[params.versions]]
   version = "v0.6.0"