ContainerImage.Pinniped/test
Andrew Keesler a4fe76f6a9
test/integration: increase confidence that a cert has rotated
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>
2020-08-28 10:20:05 -04:00
..
cluster_capabilities Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
integration test/integration: increase confidence that a cert has rotated 2020-08-28 10:20:05 -04:00
library test: fix ci failure: "no Auth Provider found for name "gcp"" 2020-08-27 09:12:34 -04:00