John Howard
John Howard
Anyhow, from a technical standpoint it's harder to add providers than other projects since we need to do CSRs. This is the "rcgen" stuff. Might be simple but need to...
@xnox do you have a specific desire to have the AWS module or to have a FIPS validated module? Id the former, would be curious to know why Currently the...
If we do this one other thing I am reminded of - boringssl and aws-lc add some onerous build steps. With boring we are able to use a pre compiled...
@xnox thanks for the additional context. Overall I think this makes sense. Here is how I would go about it: * Add a new config feature, opt-in, to build with...
(3) Yes, `--features tls-boring --no-default-features` This is due to https://github.com/istio/istio/issues/52926 not being done. COMPLIANCE_POLICY makes istid only accept 1.2, but ztunnel only accepts 1.3, so currently there is a mismatch
@gil-tohar-cyera no, this is a custom build of ztunnel - you would need to build and push your own images and point to them.
We could, although that also leaves the inverse possible broken test (only works when not run concurrently)... either way we lose. Using nextest is good for other reasons though, probably...
Thanks. This is valid, but its a documentation + dashboard error. The reporter=waypoint was an intentional decision to distinguish these
I updated `mesh` one in #52352
This is the same root cause as https://github.com/istio/istio/issues/52438 fwiw