Dynamic Varnish for Kubernetes
Updates Varnish config based on Kubernetes configuration changes. Intended for use with https://github.com/muchlearning/kubernetes-haproxy.
This pod watches Kubernetes (or more specifically, the etcd2 used by Kubernetes) for configuration changes (creates, deletes). When a change is detected, the configuration is updated, and Varnish is gracefully reloaded if needed. It uses etcd2's watch feature rather than polling, so updates should be near-instantaneous.
ETCD2BASE: (required) the base URL for the etcd2 server (with no trailing slash). The URL must be an HTTP URL; HTTPS is not (yet) supported. Defaults to
http://127.0.0.1:2379(which will probably not work).
The HAProxy configuration is driven by some Kubernetes configmaps and secrets in the
lb namespace. The pod watches these and updates the configuration when they change.
servicesconfigmap: each key defines a service to be exposed. The value is a JSON object as defined in
https://github.com/muchlearning/kubernetes-haproxy, but with the following additional keys used by the example template
varnish: an object with the following keys:
deliver: (optional) VCL to execute in the
vcl_*subroutines when a request is made for the service
varnishtemplatekey in this configmap defines a Jinja2 template to use to generate the Varnish VCL file. The template is passed these replacements:
services: a list of services, each of which is a dict corresponding to the values given in the
servicesconfigmap above. The list is sorted in the order of the service name (the keys in the
servicesconfigmap). In addition to the keys given in the service's JSON object, each service has the following keys:
name: the name of the service
env: a dict containing the process' environment variables
examples/varnish.yaml in https://github.com/muchlearning/kubernetes-haproxy.