- 27 Aug, 2020 16 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 26 Aug, 2020 23 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
This is in anticipation of removing the rule that a viking service implements an Ingress if it's the only one in the entire cluster. This can cause unexpected changes if something unrelated in the cluster is changed, for example by independent teams working in different namespaces. This makes it unnecessary to undeploy the viking service that always runs in namespace default during e2e tests (which was just such a dependency). The docs are not currently up to date on this point.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
These are internal values of the Varnish/klarlack container, which can be set differently with environment variables. Probably in nearly all deployments, they will be left with the defaults. - http target port (Varnish listener address) - varnishadm port - config check port - readiness check port - admin secret directory and file name
-
- 25 Aug, 2020 1 commit
-
-
Geoff Simmons authored
-