djpbessems
/
ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ContainerImage.Pinniped/deploy
History
Ryan Richard 6e59596285 Upon pod startup, update the Status of CredentialIssuerConfig 
- Indicate the success or failure of the cluster signing key strategy
- Also introduce the concept of "capabilities" of an integration test
  cluster to allow the integration tests to be run against clusters
  that do or don't allow the borrowing of the cluster signing key
- Tests that are not expected to pass on clusters that lack the
  borrowing of the signing key capability are now ignored by
  calling the new library.SkipUnlessClusterHasCapability test helper
- Rename library.Getenv to library.GetEnv
- Add copyrights where they were missing
 		2020-08-24 18:07:34 -07:00
..
README.md Rename project 2020-08-20 10:54:15 -07:00
crd.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
deployment.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
rbac.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
values.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00

README.md

Deploying

This example deployment uses ytt and kapp from k14s.io.

If you would rather not install these command-line tools directly on your machine, you can use alternatively get the most recent version of this container image: https://hub.docker.com/r/k14s/image/tags

  1. Fill in the values in values.yml
  2. In a terminal, cd to this deploy directory
  3. Run: ytt --file . | kapp deploy --yes --app pinniped --diff-changes --file -