John Howard
John Howard
1.24 essentially made the default behavior that way, you can see the upgrade notes that explain the minor behavioral differences: https://istio.io/latest/news/releases/1.24.x/announcing-1.24/upgrade-notes/#sidecar-scoping-changes
Can this be reopened?
Not stale, PR open in https://github.com/envoyproxy/envoy/pull/37002
I'm not super familiar with the intricacies here. For jwt we just always do this for gateway: https://github.com/istio/istio/blob/8aea55efd28f8d3348ca8529d5bd943c61de28c7/pilot/pkg/networking/plugin/authn/authentication.go#L105. Do we think it's viable to do that here? The reason I...
If you want to set a value for a single chart but not all of them, should you not be using a value other than `global.`? Like `specificChart.env=dev`
The problem is not really directly related to global flattening. In your case, you set `global.env` which Istio reads as `env` and fails. But even without flattening, Istio could read...
We've been discussing this back and forth on slack a bit for higher bandwidth, I'll update (or let @barth12 ) once we have some more complete state
Is it possible the new one gets a new IP allocated since the allocation isn't stable?
Services don't share the same IP, there is a conflict resolution mechanism to assign it a different one. So it's not a stable function but rather depends on the entire...
https://github.com/istio/istio/blob/809f73e2b3aa1b3ffcd377a44bbdf07ce3ae6094/pilot/pkg/serviceregistry/serviceentry/controller.go#L925