-
Notifications
You must be signed in to change notification settings - Fork 711
ConfigMaps for LUA extensions are not watched #6356
Copy link
Copy link
Closed
Labels
area/configIssues related to config management, e.g. Config Manager, Config Sources, etc.Issues related to config management, e.g. Config Manager, Config Sources, etc.kind/bugSomething isn't workingSomething isn't working
Milestone
Description
Description:
When using a LUA extension within an EnvoyExtensionPolicy with type: ValueRef, the LUA code is stored in a ConfigMap, this is great.
However, if the ConfigMap gets updated, Envoy Gateway doesn't notice it and thus doesn't update Envoy Proxy's configuration.
Repro steps:
- Create the ConfigMap containing some LUA code
- Create an HTTPRoute
- Create an EnvoyExtensionPolicy with the route as
targetRefand the ConfigMap asValueReffor the lua exension - Now observe envoy gateway's logs while you update the configmap, in theory you should observe the envoy gateway updating the envoy proxy configuration but nothing happens and the envoy proxy configuration is not updated.
Environment:
Using Envoy Gateway v1.4.1
Logs:
(no logs)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/configIssues related to config management, e.g. Config Manager, Config Sources, etc.Issues related to config management, e.g. Config Manager, Config Sources, etc.kind/bugSomething isn't workingSomething isn't working