DataplanePerProxy not compatible with default gatewayProxy
bewebi opened this issue · comments
Gloo Edge Product
Enterprise
Gloo Edge Version
v1.16.0
Kubernetes Version
v1.28.0
Describe the bug
dataplanePerProxy is not compatible with the default gateway-proxy
Specifically rate-limiting is not enforced, though likely other pieces will break in a similar fashion
Expected Behavior
All components of Gloo EE work when dataplanePerProxy is enabled, even when using the default gateway
Steps to reproduce the bug
Install Gloo with global.extensions.dataplanePerProxy set to true
Create a VS with rate limiting enabled
Send traffic to the VS
Observe that rate limiting is not enforced
Additional Environment Detail
This came up while investigating #9101
Additional Context
Here we hard code the ratelimitServerRef to rate-limit, but when dataplanePerProxy is enabled, the name of the default gateway's rate limit server is rate-limit-gateway-proxy
Therefore rate limit requests don't end up at an Envoy cluster that exists
We don't currently have e2e tests for dataplanePerProxy with the default gateway
@nfuden for visibility