ContainerImage.Pinniped/internal
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
..
apiserver Rename project 2020-08-20 10:54:15 -07:00
certauthority Allow app to start despite failing to borrow the cluster signing key 2020-08-25 18:22:53 -07:00
constable Add placeholder-name CLI 2020-07-28 15:15:59 -05:00
controller Allow app to start despite failing to borrow the cluster signing key 2020-08-25 18:22:53 -07:00
controllermanager Rename PinnipedDiscoveryInfo to CredentialIssuerConfig 2020-08-21 16:16:34 -07:00
downward Standardize whitespace/newlines for consistency. 2020-08-14 14:42:49 -05:00
mocks/mockcertissuer Rename project 2020-08-20 10:54:15 -07:00
provider Add tests for the new cert controllers and some other small refactorings 2020-08-10 18:53:53 -07:00
registry/credentialrequest Rename project 2020-08-20 10:54:15 -07:00
server Allow app to start despite failing to borrow the cluster signing key 2020-08-25 18:22:53 -07:00
testutil Allow app to start despite failing to borrow the cluster signing key 2020-08-25 18:22:53 -07:00