Varnish support application for Kubernetes, to automate configuration reloads (VCL) and the configuration of endpoints (Pods) as backends, to be run as a sidecar with Varnish in a Kubernetes Pod.

NOTE: WORK IN PROGRESS

  • Geoff Simmons's avatar
    Also check generated VCLs for updates, reload when updated. · c8707e3d
    Geoff Simmons authored
    Previously only files specified in the ConfigMap were checked for
    changed modification times. If only generated VCL sources were
    changed, usually due to Endpoint changes, and the VCL load failed
    for any reason, tehn afterward no changed VCL sources or changes
    in the ConfigMap were detected. This could lead to VCL never being
    updated after a change only in the generated VCLs, although the
    config does not correspond to the desired state of the cluster.
    
    Now we keep a record of the latest mtime of all VCL sources,
    including generated sources, and reload VCL if any of them are
    currently newer.
    c8707e3d
Name
Last commit
Last update
cmd Loading commit data...
container Loading commit data...
pkg Loading commit data...
.gitignore Loading commit data...
COPYING Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
go.mod Loading commit data...
go.sum Loading commit data...