Arko Dasgupta

closing this PR since its become inactive, feel free to reopen if you're still working on it

thanks for looking into this one ! the next steps here before raising a PR is designing this (doesnt need to be a design doc), but can hopefully answer these...

if you're trying to run the deployment or [daemonset](https://gateway.envoyproxy.io/docs/api/extension_types/#kubernetesdaemonsetspec) in host mode you should set `useListenerPortAsContainerPort: true` and also use the patch field to set ` hostNetwork: true` ``` apiVersion:...

@erikschul can link the relevant contour documentation for enabling something like this

I see, thanks for sharing, looks like Contour, auto populates the `hostPort` in `DaemonSet` mode. Envoy Gateway's DaemonSet mode https://gateway.envoyproxy.io/docs/api/extension_types/#kubernetesdaemonsetspec doesnt support this feature by default but you can achieve...

this should be possible with https://gateway.envoyproxy.io/docs/tasks/traffic/global-rate-limit/ Option 1 - match on `:path` sometthing like ``` rateLimit: type: Global global: rules: - clientSelectors: - headers: - name: :path value: /app limit:...

keeping this issue open so we can consider adding `path` and `method` (relates to https://github.com/envoyproxy/gateway/discussions/4448) as first class fields in the API so users dont need to rely on the...

closing this PR since its become inactive, feel free to reopen if you're still working on it

the use case sounds like Local RateLimit https://gateway.envoyproxy.io/docs/tasks/traffic/local-rate-limit/

ah thanks for the clarification