anessi

We have tested if the endpoints can be listed with the gloo service account with this commands: ``` APP_NAMESPACE=app-namespace GLOO_NAMESPACE=gloo-namespace oc auth can-i get endpoints -n $DBAN_NAMESPACE --as=system:serviceaccount:$GLOO_NAMESPACE:gloo oc auth...

This also happens on 1.11.38. We don't want to add cluster roles to the **gloo** service account. The main problem is that the Gloo POD does not come up with...

The override with `kubeResourceOverride` is a workaround, but a very ugly one because it requires to override the **whole** extauth definition due to https://github.com/solo-io/gloo/issues/5841 (e.g. single properties don't get merged...

Our main use-case is HA/failover, however, scaling may be required as well. The current Gloo Edge version does not support this, but when storing the session in Redis using Gloo...

I'd say the gateway name fits well for this value as it's defined in the `Gateway` resource. In case sharing is used (https://docs.solo.io/gloo-edge/main/introduction/architecture/deployment_arch/#sharded-api-gateway), the value would be different for each...

IMO a `namespace` is not needed as this is commonly added as generic attributes to the traces (see `resource.attributes.k8s@namespace@name` in the example below). See [example-traces.json](https://github.com/solo-io/gloo/files/14618027/example-traces.json) for two example traces, one...

@sheidkamp : thanks for the details. I don't know the internals, so if it's not possible to set any meaningful value, setting a string as you proposed above and logging...

I had another case (missing line break between two comments) ``` # -- tmp dir configuration. tmpDir: {} # -- tmpDir.sizeLimit -- Optional size limit #sizeLimit: 10M # -- logs...

This is still reproducible on version 1.15.8. The question has been raised what helm values we use for deployment. We set the following relevant values: ``` global: glooRbac: create: false...

I have created a merge request (https://github.com/helm/helm/pull/12743) that solves this issue, including tests and doc updates. However, it seems to be really hard to get hold of a maintainer to...