Seth Heidkamp

/kick doesn't seem to be an error message

Approach we will take: * When 'allow_warnings' is false, there are warnings, and we deleting a secret, we will take the following steps: 1. When validating, we will collect all...

Remaining work: - additional unit tests - 2d - PR feedback - 2d - kube e2e test - 3d - backports - 2d See ETA for how this fits on...

@DuncanDoyle We have a test release ready: ~~https://github.com/solo-io/solo-projects/actions/runs/7823727984~~ https://github.com/solo-io/solo-projects/actions/runs/7936706071 is newer It would be great to see this run with some larger/real-world configurations.

Still doing backports/solo-projects updates

OSS releases: - v1.17.0 - beta9 https://github.com/solo-io/gloo/releases/tag/v1.17.0-beta9 - v1.16.5 - https://github.com/solo-io/gloo/releases/tag/v1.16.5 Pulled in to GlooEE for release with - v1.17.0-beta1 - v.1.16.4

Hit this one again: https://github.com/solo-io/gloo/actions/runs/7410687254/job/20163550838?pr=9030 Passed on the 4th try. Seems to be failing on a different line though: ``` [FAILED] [30.019 seconds] Gloo + Istio integration tests Istio mTLS...

I want to confirm the expected behavior with a specific example, using the example from https://docs.solo.io/gloo-edge/latest/guides/observability/tracing/otel/ This is the gateway config: ``` apiVersion: gateway.solo.io/v1 kind: Gateway metadata: labels: app: gloo...

I have a solution that depends upon the gateway populating some "parent" metadata with the gateway name. This happens in the "classic" gloo gateway, and I suspect it is not...

@anessi , thanks for the feedback. I agree we shouldn't stop translating on these edge cases. However, in most of these cases I don't know that there will be a...