Seth Heidkamp

~~We're going to update the API by adding `serviceNameSource` to the `openTelemetryConfig` that will accept `gatewayName: {}` as a value, which will be used as the default if omitted.~~ ```...

Merged into 1.17/main

OSS changes have [entered PR](https://github.com/solo-io/gloo/pull/9490). In addition to adding support for configuring the individual container `securityContexts`, I have added a flag `global.podSecurityStandards.container.enableRestrictedContainerDefaults` that will default all container securityContexts to the...

@ably77 - extauth will be covered in the EE PR that relies on the OSS PR. For resources limits, that's needed at the container level, basically the same scope as...

@ably77 - looking for some additional clarifications, I see we set the resources in the `5-`/`6.5-`/`19-` jobs (for example with `gateway.cleanupJob.resources`). Can you give examples (or a full list) of...

The container security changes have been merged into EE/`solo-projects` main (will be part of the `1.17.0-beta3` release) and the 1.16.x branch (will be part of the `1.16.10` release) As requested...

Document with changes and plan: https://soloio.slab.com/posts/istio-1-21-for-gloo-edge-12jrp5yn Tests are passing CI and OSS PR should be in PR on 5/24

> Scope change can we also check out whether a bump to 1.22 would pass ci? Not committing to it but rather asking As mentioned in Slack, looks like it...

Reopening for 1.22 bump

Istio 1.22 support and test matrix added