• 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...
acl-or-auth.yaml Loading commit data...
basic-auth.yaml Loading commit data...
basic-secrets.yaml Loading commit data...
cafe_acl_or_auth.vtc Loading commit data...
cafe_basic_auth.vtc Loading commit data...
cafe_proxy_auth.vtc Loading commit data...
deploy_acl_or_auth.sh Loading commit data...
deploy_basic_auth.sh Loading commit data...
deploy_proxy_auth.sh Loading commit data...
proxy-auth-secrets.yaml Loading commit data...
proxy-auth.yaml Loading commit data...
undeploy_acl_or_auth.sh Loading commit data...
undeploy_basic_auth.sh Loading commit data...
undeploy_proxy_auth.sh Loading commit data...
verify_acl_or_auth.sh Loading commit data...
verify_basic_auth.sh Loading commit data...
verify_proxy_auth.sh Loading commit data...