djpbessems/ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2b9d2ca293
ContainerImage.Pinniped/deploy
History
Ryan Richard ca80d87dcf
Use rest.Config for discovery URL instead of env var 
- Why? Because the discovery URL is already there in the kubeconfig; let's
  not make our lives more complicated by passing it in via an env var.
- Also allow for ytt callers to not specify data.values.discovery_url - there
  are going to be a non-trivial number of installers of placeholder-name
  that want to use the server URL found in the cluster-info ConfigMap.

Signed-off-by: Andrew Keesler <akeesler@vmware.com>
2020-08-03 14:36:08 -04: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 rest.Config for discovery URL instead of env var 2020-08-03 14:36:08 -04:00
rbac.yaml Move LoginDiscoveryConfig to the crds.placeholder.suzerain-io.github.io group 2020-07-31 17:22:12 -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 -