John Howard
John Howard
Another thread claims it Just Works now with kind, so maybe this just needs testing
BTW, I don't get `A Tokio 1.x context was found, but it is being shutdown.` after upgrading -- was just an example of a type of issue that would have...
BTW turns out the error was actually still happening, opened https://github.com/open-telemetry/opentelemetry-rust/issues/1963. I missed it due to not setting the global trace provider after upgrading :facepalm:
/test integ-ambient-ipv6_istio
Yes, we spin up multiple servers in one test
We want to test `client --> {set of servers}`. https://github.com/istio/istio/blob/86057475a6e34dcdd2de9dfe8ccd8f8b483c7edc/pilot/pkg/networking/grpcgen/grpcecho_test.go#L166 Also its not the same test necessarily, its the same binary. Multiple go tests in the same package are in...
Istio identifies distinct workloads by the node Id which is a part of the bootstrap. Each one gets different config based on the node id
Can the change be reverted or fixed in a patch release? Because of how go module resolution works, we cannot depend on a module that depends on grpc 1.66+ and...
Currently we have disabled testing of proxyless gRPC
@SpectralHiss fwiw in Istio itself we have a CA_TRUSTED_NODE_ACCOUNTS that takes a list of SA's that are authorized to act in this regard (`istio-system/ztunnel` typically)