John Howard
John Howard
See the release note here: https://istio.io/latest/news/releases/1.22.x/announcing-1.22.5/#changes. There wa sa fix that caused many issues so it was reverted. A simple config like ```yaml apiVersion: networking.istio.io/v1 kind: Sidecar metadata: name: sidecar...
I see the same behavior on 1.22.3 and 1.22.5, and both work with the workaround (https://github.com/istio/istio/issues/53530#issuecomment-2412826059), and both work on master branch.
Ah, I think I got things a little mixed up. In https://github.com/hyperium/hyper/pull/3647, I sent a test and a fix. * The test was supposed to reproduce "connection is not closed...
Ok I think I figured it out and put up two PRs: * Test in hyper https://github.com/hyperium/hyper/pull/3655 * Fix in h2 https://github.com/hyperium/h2/pull/772
Lots of discussion in slack https://istio.slack.com/archives/C041EQL1XMY/p1726258013262219?thread_ts=1726157670.382619&cid=C041EQL1XMY. root cause is `POD_SECURITY_GROUP_ENFORCING_MODE: strict` which suggest likely a security group rule is being hit
Ztunnel policies: ``` - action: Deny name: converted_peer_authentication_opentelemetry-operator namespace: default rules: - - - notDestinationPorts: - 80 scope: WorkloadSelector - action: Deny name: istio_converted_static_strict namespace: istio-system rules: - - -...
/reopen Route delegation is not moving forward, this is still useful
`""`, `"-"`, `"unknown"`, `nil` - not sure. It may be usage specific, some systems have different ways to describe "not present" I would think, which makes it hard to prescribe...
@robscott I think everything you said is true, but also if you have >1 route having a name is useful. So even for a small 2 route service its helpful....