djpbessems/ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
21fd807037
ContainerImage.Pinniped/deploy
History
Ryan Richard f0c400235a
Add memory request to pinniped deployment 
- We are not setting an upper limit because Kubernetes might randomly
  decide to unschedule our pod in ways that we can't anticipate in
  advance, causing very hard to reproduce production bugs.
- We noticed that our app currently uses ~30 MB of memory when idle,
  and ~35 MB of memory under some load. So a memory request of 128
  MB should be reasonable.

Signed-off-by: Andrew Keesler <akeesler@vmware.com>
2020-08-28 15:19:16 -04:00
..
crd.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
deployment.yaml Add memory request to pinniped deployment 2020-08-28 15:19:16 -04:00
rbac.yaml Upon pod startup, update the Status of CredentialIssuerConfig 2020-08-24 18:07:34 -07:00
README.md Doc updates 2020-08-27 10:14:03 -07:00
values.yaml Doc updates 2020-08-27 10:14:03 -07:00

README.md

Deploying

Tools

This example deployment uses ytt from Carvel to template the YAML files. Either install ytt or use the container image from Dockerhub.

Procedure

  1. The configuration options are in values.yml. Fill in the values in that file, or override those values using ytt command-line options in the command below.
  2. In a terminal, cd to this deploy directory
  3. To generate the final YAML files, run: ytt --file .
  4. Deploy the generated YAML using your preferred deployment tool, such as kubectl or kapp. For example: ytt --file . | kapp deploy --yes --app pinniped --diff-changes --file -