Open bdecoste opened 1 year ago
Also tested on 1.13 with same behavior
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.12.x
Kubernetes Version
None
Describe the bug
Envoy memory increases with no traffic after deploying a set of VirtualServices, Upstreams, and RateLimitConfigs.
If the gloo pod remains up after deploying the config and the initial xDS update then the Envoy memory increases ~30-50% higher than after the initial xDS update over time.
If the gloo pod is scaled down after deploying the config and the initial xDS update so that the config has been deployed then the Envoy pod memory reaches the expected state and is stable.
Steps to reproduce the bug
TBD
Expected Behavior
Envoy memory with no traffic and no config changes stays stable
Additional Context
No response