a4fe76f6a9
It looks like requests to our aggregated API service on GKE vacillate between success and failure until they reach a converged successful state. I think this has to do with our pods updating the API serving cert at different times. If only one pod updates its serving cert to the correct value, then it should respond with success. However, the other pod would respond with failure. Depending on the load balancing algorithm that GKE uses to send traffic to pods in a service, we could end up with a success that we interpret as "all pods have rotated their certs" when it really just means "at least one pod has rotated its certs." Signed-off-by: Andrew Keesler <akeesler@vmware.com> |
||
|---|---|---|
| .. | ||
| api_discovery_test.go | ||
| api_serving_certs_test.go | ||
| app_availability_test.go | ||
| client_test.go | ||
| credentialissuerconfig_test.go | ||
| credentialrequest_test.go | ||
| kubectl_test.go | ||