djpbessems/ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e48d9faf27
ContainerImage.Pinniped/deploy
History
Ryan Richard 4cb0fd3949 Use a DaemonSet instead of a Deployment to deploy our app 
- For high availability reasons, we would like our app to scale linearly
  with the size of the control plane. Using a DaemonSet allows us to run
  one pod on each node-role.kubernetes.io/master node.
- The hope is that the Service that we create should load balance
  between these pods appropriately.
2020-08-11 17:55:34 -07:00
..
crd.yaml Move LoginDiscoveryConfig to the crds.placeholder.suzerain-io.github.io group 2020-07-31 17:22:12 -07:00
deployment.yaml Use a DaemonSet instead of a Deployment to deploy our app 2020-08-11 17:55:34 -07:00
rbac.yaml First draft of moving API server TLS cert generation to controllers 2020-08-09 10:04:05 -07:00
README.md Update deploy README.md 2020-07-07 18:50:35 -07:00
values.yaml Allow override of discovery URL via ConfigMap 2020-08-03 10:17:11 -04: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 -