John Howard
John Howard
Oh not on 1.20 though
> Tests depending on that behavior can just set the feature flag for that test, right? Yeah but they need to do a full new test suite which adds a...
`SetForTest` doesn't work in e2e tests
Unless we expose a debug interface for it :thinking: except we probably don't handle them dynamically changing (in unit tests, we change it before any setup
It should contain a lot more info. The other is demo/quickstart. We need to explain _how to operate ambient_. Things like how to attach policies to waypoints, when you should...
we need to make a similar change as done in https://github.com/istio/istio.io/commit/2e8eff90e6074bfd408604ec983f48e0bfb6134f#diff-6705e9173dca912d428d536318808ffcc77e61265a51eacd7ae5fa1246d16480L56-L112 to the other EnvoyFilter on the same page.
For reporting more IPs - blocked by https://github.com/kubernetes-sigs/gateway-api/pull/1653, which seems closed to merging. In https://github.com/istio/istio/pull/43975 I am dropping Ready since we cannot correctly implement it
Yes we should be using programmed I think. However its plausible the spec itself will change, see https://github.com/kubernetes-sigs/gateway-api/issues/1832.
Can https://github.com/istio/istio/pull/45342 just be expanded to meet all the use cases?
Why do you want it in the first place?