History

Ryan Richard ecde8fa8af Implement basic liveness and readiness probes - Call the auto-generated /healthz endpoint of our aggregated API server - Use http for liveness even though tcp seems like it might be more appropriate, because tcp probes cause TLS handshake errors to appear in our logs every few seconds - Use conservative timeouts and retries on the liveness probe to avoid having our container get restarted when it is temporarily slow due to running in an environment under resource pressure - Use less conservative timeouts and retries for the readiness probe to remove an unhealthy pod from the service less conservatively than restarting the container - Tuning the settings for retries and timeouts seem to be a mysterious art, so these are just a first draft		2020-08-17 16:44:42 -07:00
..
crd.yaml	Update a CRD validation	2020-08-17 16:29:21 -07:00
deployment.yaml	Implement basic liveness and readiness probes	2020-08-17 16:44:42 -07:00
rbac.yaml	LoginRequest -> CredentialRequest	2020-08-14 11:26:09 -04:00
README.md	Standardize whitespace/newlines for consistency.	2020-08-14 14:42:49 -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

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