ContainerImage.Pinniped/deploy
Matt Moyer 1b9a70d089
Switch back to an exec-based approach to grab the controller-manager CA. (#65)
This switches us back to an approach where we use the Pod "exec" API to grab the keys we need, rather than forcing our code to run on the control plane node. It will help us fail gracefully (or dynamically switch to alternate implementations) when the cluster is not self-hosted.

Signed-off-by: Matt Moyer <moyerm@vmware.com>
Co-authored-by: Ryan Richard <richardry@vmware.com>
2020-08-19 13:21:07 -05:00
..
README.md Standardize whitespace/newlines for consistency. 2020-08-14 14:42:49 -05:00
crd.yaml Update a CRD validation 2020-08-17 16:29:21 -07:00
deployment.yaml Switch back to an exec-based approach to grab the controller-manager CA. (#65) 2020-08-19 13:21:07 -05:00
rbac.yaml Switch back to an exec-based approach to grab the controller-manager CA. (#65) 2020-08-19 13:21:07 -05:00
values.yaml Set the `type` on the image pull `Secret` 2020-08-13 13:34:23 -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 placeholder-name --diff-changes --file -