John Howard
John Howard
`defaultHttpRetryPolicy` is availabie in https://istio.io/latest/docs/reference/config/istio.mesh.v1alpha1/. Also a valid point wrt to whether our default-defaults should change though
Is the source a sidecar? Can you check the config dump to ensure there is no somehow a duplicate istio.stats filter? cc @zirain
I think this is a dupe of https://github.com/istio/ztunnel/issues/1457
That doc is just 100% incorrect, there is no such thing as egress authorization policy in Istio and never has been. I am not sure how that doc got there...
For sidecar mode: https://istio.io/latest/docs/tasks/traffic-management/egress/egress-gateway/ For ambient: https://ambientmesh.io/docs/traffic/mesh-egress/
> hey thanks a lot @howardjohn @therealmitchconnors for confirming the behavior. On backward compatibility, let say canary revision is the leader and gateway is canary and things are working fine....
In theory we could do a check like "Only win the per-revision leader election lock if there is nothing holding the legacy lock". A bit like https://kubernetes.io/docs/concepts/cluster-administration/coordinated-leader-election/ (but not quite)....
> Even today they can race against each other There is a single pod leader, so I don't see how.
> Agree that two istiod pods in the same revision is a really niche case Hmm, actually I forgot the case if you don't use revisions. Then its not so...