You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you deploy your gateway proxies in any other namespace than gloo-system, the --name and --namespace parameters required on glooctl proxy commans is inconsistent.
Using the following configuration, in which we only deploy the default gateway in gloo-system and the other 2 gateway-proxies in gloo-external and gloo-internal, the UI will only be able to display the Envoy config of the GW in gloo-system namespace:
When you change the writeNamespace in your Gloo Edge configuration, for example to gloo-external, the glooctl proxy served-config command will show an empty result, even for the default gw-proxy:
Gloo Edge Product
Enterprise
Gloo Edge Version
1.16.6
Kubernetes Version
1.27.8
Describe the bug
When you deploy your gateway proxies in any other namespace than gloo-system, the
--name
and--namespace
parameters required onglooctl proxy
commans is inconsistent.Using the following configuration, in which we only deploy the default gateway in
gloo-system
and the other 2 gateway-proxies ingloo-external
andgloo-internal
, the UI will only be able to display the Envoy config of the GW in gloo-system namespace:To read the
served-config
of the non-default gateway-proxies ... we have to ommit the namespace:However, when we want to get the
url
oraddress
of the same proxy we do have to specify the namespace for the command to work:Note
When you change the
writeNamespace
in your Gloo Edge configuration, for example togloo-external
, theglooctl proxy served-config
command will show an empty result, even for the default gw-proxy:Specifying the value of the
writeNamespace
setting a--namespace
parameter when using this setup will return errors.Expected Behavior
Consistent use of
--name
and--namespace
inglooctl proxy
commands when deploying gateway-proxies in non-default namespaces.Steps to reproduce the bug
See Helm values in description.
Also, see reproducer project here: https://github.com/DuncanDoyle/ge-gloo-9378-9379
Additional Environment Detail
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: