Make features of VarnishConfig available to BackendConfig, as per-Service features
Features currently available for the custom resource VarnishConfig are enabled for BackendConfig as well. In particular, the current spec
elements auth
, acl
and rewrites
can be configured in BackendConfig to be applied to specific Services. This means: when Ingress rules determine that a request will be routed to a Service, then features described in BackendConfig for authorization, ACLs and rewrites are applied to them.
Going forward, this same principle will be applied for new features, such as custom error URLs as set forth in #25.
We will retain these features for VarnishConfig, so that "Varnish-wide" behavior can be defined, independent of the routing result. But BackendConfig will be a means to define all of the behavior specific to a Service.
Specifically, the self-sharding
config remains available to VarnishConfig only, since self-sharding is a property of the Varnish cluster, not of any Service.
Perhaps we should rename BackendConfig as ServiceConfig.
This change may make issue #23 (closed) obsolete, since the idea in mind was to separate configs to be applied to individual Services.