- 22 Apr, 2021 4 commits
-
-
Nils Goroll authored
-
Geoff Simmons authored
-
Geoff Simmons authored
This functions exactly like the recently added feature for the viking service. The probes are fixed, but properties such as timeouts, delays, and success/failure thresholds can be set in values.yaml for the controller. k8s defaults hold for values that are not set. Closes #41
-
Geoff Simmons authored
-
- 19 Apr, 2021 1 commit
-
-
Nils Goroll authored
-
- 18 Apr, 2021 3 commits
-
-
Nils Goroll authored
I was not aware that they obviously are bashisms
-
Nils Goroll authored
-
Nils Goroll authored
-
- 12 Apr, 2021 4 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
2.0 is no longer available on ftp.debian.org/debian/dists/buster-backports/
-
Nils Goroll authored
I do not understand why ./bootstrap.sh ends up as 444 when it is checked into git as 755
-
Nils Goroll authored
https://gitlab.com/uplex/varnish/k8s-ingress/-/jobs/1171216645 $ go get -d github.com/slimhazard/gogitversion go: downloading github.com/slimhazard/gogitversion v0.0.0-20180821215210-78330f1af7fc go: github.com/slimhazard/gogitversion upgrade => v0.0.0-20180821215210-78330f1af7fc $ pushd $GOPATH/pkg/mod/github.com/slimhazard/gogitversion* /go/pkg/mod/github.com/slimhazard/gogitversion@v0.0.0-20180821215210-78330f1af7fc /builds/uplex/varnish/k8s-ingress $ make install go generate gogitversion.go:40: running "./bootstrap.sh": fork/exec ./bootstrap.sh: permission denied make: *** [Makefile:30: all] Error 1
-
- 01 Apr, 2021 1 commit
-
-
Geoff Simmons authored
The probes themselves are fixed, but it is now possible to set such properties as timeouts, delays, success/failure thresholds etc in values.yaml. k8s defaults hold for values that are not set. Closes #41
-
- 22 Mar, 2021 1 commit
-
-
Nils Goroll authored
-
- 21 Feb, 2021 5 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
Update the docs while we're here: - Add incompleteRetryDelay. - Remove templatedir. - Remove the glog flags, which are no longer added to the controller flags.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 20 Feb, 2021 1 commit
-
-
Geoff Simmons authored
Forgot it in the previous commit.
-
- 19 Feb, 2021 8 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
The TemplateConfig resource is only read by the controller's k8s client when the devmode CLI flag is set. The TemplateConfig spec has fields for the various templates for VCL generation: ingress, self-sharding, ACL etc. The value type for all of those fields is string, and each field is optional. When a TemplateConfig specifies a value for a template type, the controller attempts to parse it as a text/template.Template, using the same function map defined for the template type. If the parse fails, then the error is logged and an Event type Warning with the error message is generated, and the field is ignored. If the parse succeeds, then the template is replaced for all further VCL generation by the controller. When a TemplateConfig is deleted, then for each template type that it specifies, the template is reverted to the controller's standard value. In this first iteration: - only the ACL template is updated, will add the other types. - only kubectl deployments are supported, will add support in the helm chart for the viking controller. - we have an e2e test, but it is not yet added to the e2e script that runs all of them, or to the gitlab CI script, since these have to support helm deployments.
-
Geoff Simmons authored
-
- 15 Feb, 2021 4 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
Use a diff package for verbose error display when a gold file does not match. This has been especially difficult when there are whitespace mismatches. Encapsulate the test idiom in a single function. Lotsa DRY. Tidy up the module list while we're here.
-
- 11 Feb, 2021 1 commit
-
-
Geoff Simmons authored
This makes the code less verbose, and more efficient, since the shard parameters don't need to be fully recomputed each time. Closes #26
-
- 24 Jan, 2021 1 commit
-
-
Nils Goroll authored
-
- 14 Jan, 2021 3 commits
-
-
Geoff Simmons authored
Now consistent with the naming of IngressBackends. Adds the vk8s_ prefix, the namespace and port to the name.
-
Geoff Simmons authored
This had been done by querying Pods. It's enough just to query Endpoints.
-
Geoff Simmons authored
-
- 13 Jan, 2021 1 commit
-
-
Geoff Simmons authored
-
- 07 Jan, 2021 1 commit
-
-
Geoff Simmons authored
This was a remnant of earlier versions when the Pods were set to not Ready when there is no Ingress to implement. No the Pods are always ready, but we set the "configured" endpoint to respond with non-200 when nothing is defined. However, if an Ingress had been defined previously, then deleted, the http/https endpoints still responded as for the previous config. This was semantically incorrect, and also meant that the VCL config remained defined indefinitely. Now it becomes unlabeled, so it can go cold and then be discarded.
-
- 06 Jan, 2021 1 commit
-
-
Geoff Simmons authored
-