Ben Leggett
Ben Leggett
Aight so current consensus: https://docs.google.com/document/d/1SMlwliEnthgq7r2PjpLl1kCq3t8rAMbgu6r_lDAXJ0w/edit#heading=h.ttmnrtyxr98j - we aren't going to document the wrapper chart (gonna close this PR) - The wrapper chart is published under `samples`: https://github.com/istio/release-builder/pull/1901 but I am...
We should also talk about: https://github.com/istio/istio/discussions/51588#discussioncomment-9796772 Also impacts netpol (depending on the CNI), also a thing.
:+1: on not using "ztunnel" in architecture documents. - `node proxy` (preferred, it describes (location) (function) which is enough) - `L4 proxy` We only need terms to describe our current...
`bpf-lb-sock-hostns-only: "true"` I am not 100% sure that this is still required, it's an inherited leftover from the pre-Ambient attempts to get Cilium and Istio working together. From the description...
Also https://github.com/istio/ztunnel/issues/864
works for me as long as multiarch build support is at-least-as-robust as boring, hopefully less painful.
Can we just use `nextest` in CI? I don't see why not.
> We could, although that also leaves the inverse possible broken test (only works when not run concurrently)... either way we lose. Fine with that tradeoff, as those sorts of...
We should be able to use `cargo test -- --shuffle` eventually to flag flakes faster without `nextest` - currently that's behind `unstable/nightly` tho, better to wait for that.