diff --git a/api/v1alpha1/envoygateway_types.go b/api/v1alpha1/envoygateway_types.go index df7b8eae33c..b96218f0746 100644 --- a/api/v1alpha1/envoygateway_types.go +++ b/api/v1alpha1/envoygateway_types.go @@ -160,7 +160,7 @@ type EnvoyGatewayProvider struct { // EnvoyGatewayKubernetesProvider defines configuration for the Kubernetes provider. type EnvoyGatewayKubernetesProvider struct { // RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. - // If unspecified, default settings for the manged Envoy ratelimit deployment resource + // If unspecified, default settings for the managed Envoy ratelimit deployment resource // are applied. // // +optional diff --git a/api/v1alpha1/envoyproxy_types.go b/api/v1alpha1/envoyproxy_types.go index dd0f2f1447a..575eb2b9e08 100644 --- a/api/v1alpha1/envoyproxy_types.go +++ b/api/v1alpha1/envoyproxy_types.go @@ -109,14 +109,14 @@ type EnvoyProxyProvider struct { // provider. type EnvoyProxyKubernetesProvider struct { // EnvoyDeployment defines the desired state of the Envoy deployment resource. - // If unspecified, default settings for the manged Envoy deployment resource + // If unspecified, default settings for the managed Envoy deployment resource // are applied. // // +optional EnvoyDeployment *KubernetesDeploymentSpec `json:"envoyDeployment,omitempty"` // EnvoyService defines the desired state of the Envoy service resource. - // If unspecified, default settings for the manged Envoy service resource + // If unspecified, default settings for the managed Envoy service resource // are applied. // // +optional diff --git a/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoyproxies.yaml b/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoyproxies.yaml index d1553ef5f84..f9ef4470640 100644 --- a/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoyproxies.yaml +++ b/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoyproxies.yaml @@ -119,7 +119,7 @@ spec: envoyDeployment: description: EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings - for the manged Envoy deployment resource are applied. + for the managed Envoy deployment resource are applied. properties: container: description: Container defines the resources and securityContext @@ -3800,7 +3800,7 @@ spec: envoyService: description: EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings - for the manged Envoy service resource are applied. + for the managed Envoy service resource are applied. properties: allocateLoadBalancerNodePorts: description: AllocateLoadBalancerNodePorts defines if diff --git a/docs/latest/api/extension_types.md b/docs/latest/api/extension_types.md index 0c9c0ca74d2..2f47c3f89f8 100644 --- a/docs/latest/api/extension_types.md +++ b/docs/latest/api/extension_types.md @@ -301,7 +301,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the manged Envoy ratelimit deployment resource are applied. | +| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the managed Envoy ratelimit deployment resource are applied. | | `watch` _[KubernetesWatchMode](#kuberneteswatchmode)_ | Watch holds configuration of which input resources should be watched and reconciled. | | `deploy` _[KubernetesDeployMode](#kubernetesdeploymode)_ | Deploy holds configuration of how output managed resources such as the Envoy Proxy data plane should be deployed | | `overwrite_control_plane_certs` _boolean_ | OverwriteControlPlaneCerts updates the secrets containing the control plane certs, when set. | @@ -491,8 +491,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the manged Envoy deployment resource are applied. | -| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the manged Envoy service resource are applied. | +| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the managed Envoy deployment resource are applied. | +| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the managed Envoy service resource are applied. | ## EnvoyProxyProvider diff --git a/docs/latest/design/accesslog.md b/docs/latest/design/accesslog.md index 89aeec39153..16882cd4d5a 100644 --- a/docs/latest/design/accesslog.md +++ b/docs/latest/design/accesslog.md @@ -4,7 +4,7 @@ Envoy supports extensible accesslog to different sinks, File, gRPC etc. Envoy supports customizable access log formats using predefined fields as well as arbitrary HTTP request and response headers. Envoy supports several built-in access log filters and extension filters that are registered at runtime. -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`. ## Goals diff --git a/docs/latest/design/client-traffic-policy.md b/docs/latest/design/client-traffic-policy.md index fd2a4eebf54..f4bc5c213ee 100644 --- a/docs/latest/design/client-traffic-policy.md +++ b/docs/latest/design/client-traffic-policy.md @@ -95,7 +95,7 @@ it targets a specific Listener within a `Gateway` and Policy B has a `targetRef` entire Gateway then * Policy A will be applied/attached to the specific Listener defined in the `targetRef.SectionName` * Policy B will be applied to the remaining Listeners within the Gateway. Policy B will have an additional - status condition `Overriden=True`. + status condition `Overridden=True`. ## Alternatives * The project can indefintely wait for these configuration parameters to be part of the [Gateway API]. diff --git a/docs/latest/design/metrics.md b/docs/latest/design/metrics.md index d4ce03c4d8a..5be5942d570 100644 --- a/docs/latest/design/metrics.md +++ b/docs/latest/design/metrics.md @@ -8,7 +8,7 @@ Envoy enables prometheus format output via the `/stats/prometheus` [admin endpoi Envoy support different kinds of sinks, but EG will only support [Open Telemetry sink](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/stat_sinks/open_telemetry/v3/open_telemetry.proto). -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`. ## Goals diff --git a/docs/latest/design/rate-limit.md b/docs/latest/design/rate-limit.md index 10ef7a3fc93..fb326b080b2 100644 --- a/docs/latest/design/rate-limit.md +++ b/docs/latest/design/rate-limit.md @@ -381,7 +381,7 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP ### Global Rate limiting * [Global rate limiting][] in Envoy Proxy can be achieved using the following - - * [Actions][] can be conifgured per [xDS Route][]. + * [Actions][] can be configured per [xDS Route][]. * If the match criteria defined within these actions is met for a specific HTTP Request, a set of key value pairs called [descriptors][] defined within the above actions is sent to a remote [rate limit service][], whose configuration (such as the URL for the rate limit service) is defined using a [rate limit filter][]. diff --git a/docs/latest/design/request-authentication.md b/docs/latest/design/request-authentication.md index 7f75fa07291..6b2192eadfd 100644 --- a/docs/latest/design/request-authentication.md +++ b/docs/latest/design/request-authentication.md @@ -8,7 +8,7 @@ will be rejected if it contains invalid authentication information, based on the proposed in this design document. Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and -implementation-specific API [support levels][] for implementors such as Envoy Gateway to expose features. Since +implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since implementing request authentication is not covered by `Core` or `Extended` APIs, an `Implementation-specific` API will be created for this purpose. diff --git a/docs/latest/design/tracing.md b/docs/latest/design/tracing.md index 46a6995d336..5458b163157 100644 --- a/docs/latest/design/tracing.md +++ b/docs/latest/design/tracing.md @@ -4,7 +4,7 @@ Envoy supports extensible tracing to different sinks, Zipkin, OpenTelemetry etc. Overview of Envoy tracing can be found [here](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/observability/tracing). -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`. Only OpenTelemetry sink can be configured currently, you can use [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) to export to other tracing backends. diff --git a/docs/latest/releases/v0.5.md b/docs/latest/releases/v0.5.md index 733a8e6bf1b..8c7b72cd53b 100644 --- a/docs/latest/releases/v0.5.md +++ b/docs/latest/releases/v0.5.md @@ -39,7 +39,7 @@ The release adds a ton of features and functionality. Here are some highlights: ### Ratelimiting + Added Support for Distinct Ratelimiting Based On IP Addresses -+ Added upport for JWT Claim based Ratelimiting ++ Added Support for JWT Claim based Ratelimiting + Switched to Xds SOTW Server for RateLimit Service Configuration ### API Updates diff --git a/docs/latest/user/envoy-patch-policy.md b/docs/latest/user/envoy-patch-policy.md index 10a1a2d0ccb..6d70ffd07db 100644 --- a/docs/latest/user/envoy-patch-policy.md +++ b/docs/latest/user/envoy-patch-policy.md @@ -18,7 +18,7 @@ not exposed by Envoy Gateway APIs today. ## Quickstart -### Prerequistes +### Prerequisites * Follow the steps from the [Quickstart](quickstart.md) guide to install Envoy Gateway and the example manifest. Before proceeding, you should be able to query the example backend using HTTP. diff --git a/docs/v0.3.0/api/config_types.md b/docs/v0.3.0/api/config_types.md index e1e08a15a60..8ddc73d3efc 100644 --- a/docs/v0.3.0/api/config_types.md +++ b/docs/v0.3.0/api/config_types.md @@ -141,7 +141,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the manged Envoy deployment resource are applied. | +| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the managed Envoy deployment resource are applied. | ## LogComponent diff --git a/docs/v0.3.0/design/ratelimit.md b/docs/v0.3.0/design/ratelimit.md index a88021f7c71..8cf069346e4 100644 --- a/docs/v0.3.0/design/ratelimit.md +++ b/docs/v0.3.0/design/ratelimit.md @@ -265,7 +265,7 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP ### Global Rate limiting * [Global rate limiting][] in Envoy Proxy can be achieved using the following - - * [Actions][] can be conifgured per [xDS Route][]. + * [Actions][] can be configured per [xDS Route][]. * If the match criteria defined within these actions is met for a specific HTTP Request, a set of key value pairs called [descriptors][] defined within the above actions is sent to a remote [rate limit service][], whose configuration (such as the URL for the rate limit service) is defined using a [rate limit filter][]. diff --git a/docs/v0.3.0/design/request-authentication.md b/docs/v0.3.0/design/request-authentication.md index 50490fdb5eb..dd269771cc1 100644 --- a/docs/v0.3.0/design/request-authentication.md +++ b/docs/v0.3.0/design/request-authentication.md @@ -8,7 +8,7 @@ will be rejected if it contains invalid authentication information, based on the proposed in this design document. Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and -implementation-specific API [support levels][] for implementors such as Envoy Gateway to expose features. Since +implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since implementing request authentication is not covered by `Core` or `Extended` APIs, an `Implementation-specific` API will be created for this purpose. diff --git a/docs/v0.4.0/api/config_types.md b/docs/v0.4.0/api/config_types.md index 87118b7dbe4..2764ba82300 100644 --- a/docs/v0.4.0/api/config_types.md +++ b/docs/v0.4.0/api/config_types.md @@ -53,7 +53,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the manged Envoy ratelimit deployment resource are applied. | +| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the managed Envoy ratelimit deployment resource are applied. | ## EnvoyGatewayProvider @@ -116,8 +116,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the manged Envoy deployment resource are applied. | -| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the manged Envoy service resource are applied. | +| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the managed Envoy deployment resource are applied. | +| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the managed Envoy service resource are applied. | ## EnvoyProxyProvider diff --git a/docs/v0.4.0/design/rate-limit.md b/docs/v0.4.0/design/rate-limit.md index b3e88e2ae99..7aaa226cf45 100644 --- a/docs/v0.4.0/design/rate-limit.md +++ b/docs/v0.4.0/design/rate-limit.md @@ -310,7 +310,7 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP ### Global Rate limiting * [Global rate limiting][] in Envoy Proxy can be achieved using the following - - * [Actions][] can be conifgured per [xDS Route][]. + * [Actions][] can be configured per [xDS Route][]. * If the match criteria defined within these actions is met for a specific HTTP Request, a set of key value pairs called [descriptors][] defined within the above actions is sent to a remote [rate limit service][], whose configuration (such as the URL for the rate limit service) is defined using a [rate limit filter][]. diff --git a/docs/v0.4.0/design/request-authentication.md b/docs/v0.4.0/design/request-authentication.md index 7f75fa07291..6b2192eadfd 100644 --- a/docs/v0.4.0/design/request-authentication.md +++ b/docs/v0.4.0/design/request-authentication.md @@ -8,7 +8,7 @@ will be rejected if it contains invalid authentication information, based on the proposed in this design document. Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and -implementation-specific API [support levels][] for implementors such as Envoy Gateway to expose features. Since +implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since implementing request authentication is not covered by `Core` or `Extended` APIs, an `Implementation-specific` API will be created for this purpose. diff --git a/docs/v0.5.0/api/config_types.md b/docs/v0.5.0/api/config_types.md index 73d2ace5762..9ce37099fdc 100644 --- a/docs/v0.5.0/api/config_types.md +++ b/docs/v0.5.0/api/config_types.md @@ -177,7 +177,7 @@ _Appears in:_ | Field | Description | | --- | --- | -| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the manged Envoy ratelimit deployment resource are applied. | +| `rateLimitDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | RateLimitDeployment defines the desired state of the Envoy ratelimit deployment resource. If unspecified, default settings for the managed Envoy ratelimit deployment resource are applied. | | `watch` _[KubernetesWatchMode](#kuberneteswatchmode)_ | Watch holds configuration of which input resources should be watched and reconciled. | | `deploy` _[KubernetesDeployMode](#kubernetesdeploymode)_ | Deploy holds configuration of how output managed resources such as the Envoy Proxy data plane should be deployed | | `overwrite_control_plane_certs` _boolean_ | OverwriteControlPlaneCerts updates the secrets containing the control plane certs, when set. | @@ -288,8 +288,8 @@ _Appears in:_ | Field | Description | | --- | --- | -| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the manged Envoy deployment resource are applied. | -| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the manged Envoy service resource are applied. | +| `envoyDeployment` _[KubernetesDeploymentSpec](#kubernetesdeploymentspec)_ | EnvoyDeployment defines the desired state of the Envoy deployment resource. If unspecified, default settings for the managed Envoy deployment resource are applied. | +| `envoyService` _[KubernetesServiceSpec](#kubernetesservicespec)_ | EnvoyService defines the desired state of the Envoy service resource. If unspecified, default settings for the managed Envoy service resource are applied. | ## EnvoyProxyProvider diff --git a/docs/v0.5.0/design/accesslog.md b/docs/v0.5.0/design/accesslog.md index 62cf8170704..6d8b9d0c218 100644 --- a/docs/v0.5.0/design/accesslog.md +++ b/docs/v0.5.0/design/accesslog.md @@ -4,7 +4,7 @@ Envoy supports extensible accesslog to different sinks, File, gRPC etc. Envoy supports customizable access log formats using predefined fields as well as arbitrary HTTP request and response headers. Envoy supports several built-in access log filters and extension filters that are registered at runtime. -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since accesslog is not covered by `Core` or `Extended` APIs, EG should provide an easy to config access log formats and sinks per `EnvoyProxy`. ## Goals diff --git a/docs/v0.5.0/design/metrics.md b/docs/v0.5.0/design/metrics.md index e01260bcd19..2a2924a993a 100644 --- a/docs/v0.5.0/design/metrics.md +++ b/docs/v0.5.0/design/metrics.md @@ -8,7 +8,7 @@ Envoy enables prometheus format output via the `/stats/prometheus` [admin endpoi Envoy support different kinds of sinks, but EG will only support [Open Telemetry sink](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/stat_sinks/open_telemetry/v3/open_telemetry.proto). -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since metrics is not covered by `Core` or `Extended` APIs, EG should provide an easy to config metrics per `EnvoyProxy`. ## Goals diff --git a/docs/v0.5.0/design/rate-limit.md b/docs/v0.5.0/design/rate-limit.md index 10ef7a3fc93..fb326b080b2 100644 --- a/docs/v0.5.0/design/rate-limit.md +++ b/docs/v0.5.0/design/rate-limit.md @@ -381,7 +381,7 @@ attribute such as [IP subnet][] in the future that are not relevant in the [HTTP ### Global Rate limiting * [Global rate limiting][] in Envoy Proxy can be achieved using the following - - * [Actions][] can be conifgured per [xDS Route][]. + * [Actions][] can be configured per [xDS Route][]. * If the match criteria defined within these actions is met for a specific HTTP Request, a set of key value pairs called [descriptors][] defined within the above actions is sent to a remote [rate limit service][], whose configuration (such as the URL for the rate limit service) is defined using a [rate limit filter][]. diff --git a/docs/v0.5.0/design/request-authentication.md b/docs/v0.5.0/design/request-authentication.md index 7f75fa07291..6b2192eadfd 100644 --- a/docs/v0.5.0/design/request-authentication.md +++ b/docs/v0.5.0/design/request-authentication.md @@ -8,7 +8,7 @@ will be rejected if it contains invalid authentication information, based on the proposed in this design document. Envoy Gateway leverages [Gateway API][] for configuring managed Envoy proxies. Gateway API defines core, extended, and -implementation-specific API [support levels][] for implementors such as Envoy Gateway to expose features. Since +implementation-specific API [support levels][] for implementers such as Envoy Gateway to expose features. Since implementing request authentication is not covered by `Core` or `Extended` APIs, an `Implementation-specific` API will be created for this purpose. diff --git a/docs/v0.5.0/design/tracing.md b/docs/v0.5.0/design/tracing.md index 4b85cff2287..73d7b94ce21 100644 --- a/docs/v0.5.0/design/tracing.md +++ b/docs/v0.5.0/design/tracing.md @@ -4,7 +4,7 @@ Envoy supports extensible tracing to different sinks, Zipkin, OpenTelemetry etc. Overview of Envoy tracing can be found [here](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/observability/tracing). -Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementors such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`. +Envoy Gateway leverages [Gateway API](https://gateway-api.sigs.k8s.io/) for configuring managed Envoy proxies. Gateway API defines core, extended, and implementation-specific API [support levels](https://gateway-api.sigs.k8s.io/concepts/conformance/?h=extended#2-support-levels) for implementers such as Envoy Gateway to expose features. Since tracing is not covered by `Core` or `Extended` APIs, EG should provide an easy to config tracing per `EnvoyProxy`. Only OpenTelemetry sink can be configured currently, you can use [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) to export to other tracing backends. diff --git a/docs/v0.5.0/releases/v0.5.md b/docs/v0.5.0/releases/v0.5.md index 733a8e6bf1b..8c7b72cd53b 100644 --- a/docs/v0.5.0/releases/v0.5.md +++ b/docs/v0.5.0/releases/v0.5.md @@ -39,7 +39,7 @@ The release adds a ton of features and functionality. Here are some highlights: ### Ratelimiting + Added Support for Distinct Ratelimiting Based On IP Addresses -+ Added upport for JWT Claim based Ratelimiting ++ Added Support for JWT Claim based Ratelimiting + Switched to Xds SOTW Server for RateLimit Service Configuration ### API Updates diff --git a/docs/v0.5.0/user/envoy-patch-policy.md b/docs/v0.5.0/user/envoy-patch-policy.md index 0bd19d510bd..efabd72f5f1 100644 --- a/docs/v0.5.0/user/envoy-patch-policy.md +++ b/docs/v0.5.0/user/envoy-patch-policy.md @@ -18,7 +18,7 @@ not exposed by Envoy Gateway APIs today. ## Quickstart -### Prerequistes +### Prerequisites * Follow the steps from the [Quickstart](quickstart.md) guide to install Envoy Gateway and the example manifest. Before proceeding, you should be able to query the example backend using HTTP. diff --git a/internal/gatewayapi/testdata/gateway-with-listener-with-invalid-multiple-tls-configuration.out.yaml b/internal/gatewayapi/testdata/gateway-with-listener-with-invalid-multiple-tls-configuration.out.yaml index af5098c227e..aaa21059be6 100644 --- a/internal/gatewayapi/testdata/gateway-with-listener-with-invalid-multiple-tls-configuration.out.yaml +++ b/internal/gatewayapi/testdata/gateway-with-listener-with-invalid-multiple-tls-configuration.out.yaml @@ -32,7 +32,7 @@ gateways: conditions: - lastTransitionTime: null message: Secret envoy-gateway/tls-secret-ecdsa-2 public key algorithm must - be unique, matched cerificate FQDN [foo.bar.com] has a conficting algorithm + be unique, matched certificate FQDN [foo.bar.com] has a conflicting algorithm [ECDSA]. reason: InvalidCertificateRef status: "False" diff --git a/internal/gatewayapi/tls.go b/internal/gatewayapi/tls.go index c04dc967d97..e9c9199e79f 100644 --- a/internal/gatewayapi/tls.go +++ b/internal/gatewayapi/tls.go @@ -50,7 +50,7 @@ func validateTLSSecretsData(secrets []*corev1.Secret, host *v1beta1.Hostname) er // Check whether the public key algorithm and matched certificate FQDN in the referenced secrets are unique. if matchedFQDN, ok := pkaSecretSet[pkaSecretKey]; ok { - return fmt.Errorf("%s/%s public key algorithm must be unique, matched cerificate FQDN %s has a conficting algorithm [%s]", + return fmt.Errorf("%s/%s public key algorithm must be unique, matched certificate FQDN %s has a conflicting algorithm [%s]", secret.Namespace, secret.Name, matchedFQDN, publicKeyAlgorithm) } diff --git a/internal/ir/xds.go b/internal/ir/xds.go index 13da14e1331..b2884c04fbe 100644 --- a/internal/ir/xds.go +++ b/internal/ir/xds.go @@ -885,7 +885,7 @@ type OpenTelemetryAccessLog struct { type EnvoyPatchPolicy struct { EnvoyPatchPolicyStatus // JSONPatches are the JSON Patches that - // are to be applied to generaed Xds linked to the gateway. + // are to be applied to generated Xds linked to the gateway. JSONPatches []*JSONPatchConfig `json:"jsonPatches,omitempty" yaml:"jsonPatches,omitempty"` } diff --git a/tools/src/codespell/requirements.txt b/tools/src/codespell/requirements.txt index ddff454685c..e0a43e13840 100644 --- a/tools/src/codespell/requirements.txt +++ b/tools/src/codespell/requirements.txt @@ -1 +1 @@ -codespell==2.2.5 +codespell==2.2.6