John Howard
John Howard
Istio on master doesn't use hostNetwork which may move this one step closer.
idea: add a custom json unmarshaller *upstream* to either translate or ignore it
fixed by https://github.com/istio/istio/pull/53993
thats not right
I put a hold due to 2024‑10‑29 → 2024‑08‑02 (note its downgrading, not upgrading). The prow image publishing upstream is basically broken for 4 months, still pending a fix.
config_dump does too, not as giant though
> The intent here is to give implementations a way to say "hey, you're running with a version I don't support, maybe check that before logging a support issue". That...
> So... overall, I feel like neither of these hold together all that well, which makes me wonder what I'm missing. 🙂 Its slightly worse than your examples actually --...
I have a few issues: * I don't think resource status should replace documentation. Resource status should be used, essentially, as asynchronous validation webhook type workflows. Its hard for me...
> Spitballing here, but this could involve a supportedVersions struct in GWC status, conceptually similar to supportedFeatures, and that would allow implementations to signal the combination of Gateway API versions...