- 30 Jun, 2020 7 commits
-
-
Geoff Simmons authored
Ref gitlab issue #20
-
Geoff Simmons authored
Uses VMOD dynamic, and requires that the getdns library is installed in the image running Varnish. This allows us to use dynamic.resolve(), in particular so that TTLs from DNS are honored. Currently sets ttl to a hard-wired value of 30s. Since the TTLs for lookup are obtained from DNS, this actually sets the delay until lookups are retried after negative results (default 1h). The next step is to test and extend BackendConfig support to configure properties of VMOD dynamic. That will make it possible to configure the ttl value (although we might stay with a much shorter ttl than 1h). Partially addresses gitlab issue #20.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 18 Jun, 2020 1 commit
-
-
Lars Fenneberg authored
-
- 12 Jun, 2020 6 commits
-
-
Geoff Simmons authored
These weren't necessarily being changed after an Endpoints update.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
The Ingress update may have followed an update for Endpoints.
-
Geoff Simmons authored
XXX: re-use this code wherever we wait for port-forward.
-
- 11 Jun, 2020 2 commits
-
-
Emanuel Winblad authored
-
Emanuel Winblad authored
-
- 10 Jun, 2020 2 commits
-
-
Geoff Simmons authored
-
Lars Fenneberg authored
-
- 05 Jun, 2020 1 commit
-
-
Geoff Simmons authored
-
- 04 Jun, 2020 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
For that, the Secret must be named as the TLS Secret by an Ingress in the same namespace that identifies out ingress.class. This means that the controller doesn't need to try delete an element from any PEM Secret (to remove the certificate from the haproxy Secret volume).
-
- 03 Jun, 2020 9 commits
-
-
Geoff Simmons authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
Lars Fenneberg authored
-
- 02 Jun, 2020 2 commits
-
-
Geoff Simmons authored
-
Lars Fenneberg authored
-
- 28 May, 2020 8 commits
-
-
Geoff Simmons authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Geoff Simmons authored
For the Unix domain socket over which haproxy and varnish communicate, we have chmod 660 and chgrp varnish. haproxy belongs to group varnish and thus has write permissions on the socket, which is required in Linux to be able to connect. For that, both containers must have the same group name and GID. We've been using 998, since that results from the RPM install for Varnish from the official packagecloud repos.
-
Tim Leers authored
-