• Geoff Simmons's avatar
    Redefine the labels used to identify relevant Secrets. · 18abf575
    Geoff Simmons authored
    Use the label key viking.uplex.de/secret. The controller only reads
    Secrets with this label, and with the field type:kubernetes.io/tls
    (the latter are Secrets specified for Ingress).
    
    Three values are permitted for the label:
    
    admin: credentials for remote admin of Varnish and haproxy (Varnish
    shared secret and Basic Auth password for the dataplane API).
    
    pem: initially empty Secret into which the controller writes pem
    files (concatenated crt and key), projected into a volume from
    which haproxy reads at load time. Currently only with the hard-
    wired name "tls-cert", so that RBAC update privileges can be
    limited to this Secret.
    
    auth: credentials for Basic and Proxy Auth, as configured via
    the VarnishConfig custom resource.
    18abf575
Name
Last commit
Last update
..
README.md Loading commit data...
adm-secret-coffee.yaml Loading commit data...
adm-secret-tea.yaml Loading commit data...
admin-svc-coffee.yaml Loading commit data...
admin-svc-tea.yaml Loading commit data...
cafe.vtc Loading commit data...
coffee-ingress.yaml Loading commit data...
coffee.yaml Loading commit data...
deploy.sh Loading commit data...
multi-varnish-ns.odg Loading commit data...
multi-varnish-ns.png Loading commit data...
namespace.yaml Loading commit data...
nodeport-coffee.yaml Loading commit data...
nodeport-tea.yaml Loading commit data...
tea-ingress.yaml Loading commit data...
tea.yaml Loading commit data...
tls-cert-secret.yaml Loading commit data...
undeploy.sh Loading commit data...
varnish-coffee.yaml Loading commit data...
varnish-tea.yaml Loading commit data...
verify.sh Loading commit data...