ContainerImage.Pinniped/test/library
Ryan Richard 80153f9a80 Allow app to start despite failing to borrow the cluster signing key
- Controller and aggregated API server are allowed to run
- Keep retrying to borrow the cluster signing key in case the failure
  to get it was caused by a transient failure
- The CredentialRequest endpoint will always return an authentication
  failure as long as the cluster signing key cannot be borrowed
- Update which integration tests are skipped to reflect what should
  and should not work based on the cluster's capability under this
  new behavior
- Move CreateOrUpdateCredentialIssuerConfig() and related methods
  to their own file
- Update the CredentialIssuerConfig's Status every time we try to
  refresh the cluster signing key
2020-08-25 18:22:53 -07:00
..
client.go test/library: try another cert rest config 2020-08-24 11:01:37 -04:00
cluster_capabilities.go Allow app to start despite failing to borrow the cluster signing key 2020-08-25 18:22:53 -07:00
env.go Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
skip.go Use Go's -short flag as a way to avoid running integration tests. 2020-08-06 20:44:14 -05:00
spew.go Add integration test to check app is running 2020-07-09 15:30:59 -04:00