Kubernetes Ingress Controller based on Varnish NOTE: WORK IN PROGRESS

  • Nils Goroll's avatar
    fix resolve= parameter for self-sharding · 49650e70
    Nils Goroll authored
    in vcl_backend_response {} and vcl_backend_error {} we test if
    `bereq.backend == vk8s_cluster.backend(resolve=LAZY)`. With the
    current code, this condition will never evaluate true, because
    `resolve=NOW` will make the shard director return the "real" (VBE)
    backend.
    
    With this patch, the net effect, the chosen cluster varnish backend,
    should still be the same, except for the rare race event that the
    backend becomes unhealthy between the time the vcl code executes and
    when the backend connection is made. We already account for this race
    by setting `req.hash_ignore_busy` in vcl_revc {}.
    49650e70
Name
Last commit
Last update
charts Loading commit data...
cmd Loading commit data...
container Loading commit data...
deploy Loading commit data...
docs Loading commit data...
examples Loading commit data...
hack Loading commit data...
pkg Loading commit data...
test Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
.kind-gitlab.yaml 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...