I believe this became necessary because the meaning of the state
and temperature fields in vcl.list has changed in recent Varnish
versions (which we are now using).

This makes backend names more readily recognizable in VCL sources,
and as used in tools such as varnishlog and varnishstat. If the
Pod ns/name is not available, fall back to the previous scheme of
generating names from the Endpoint network addresses.

This makes the naming for Varnish and IngressBackend instances more
legible, and more readily associated with the Pods on which they run,
than by using only network addresses.

First use the names in the controller logs.

This is possible now that we are using Varnish versions that support
return(error(404)) from the backend side. It eliminates unnecessary
computation when a request leads to a cache hit or synthetic response.

It also simplifies the generated VCL code, since the evaluation
happens in one place, rather than in each of hit, miss, pass and
pipe.

Cached responses were interfering with other tests when the e2e test
script was run.

Type declarations in struct literals are unnecessary where the type
is unambiguous.

Forgot it in the previous commit.

Also set up the tests so that the external IP and port for both the
NodePort and LoadBalancer tests. For this it is necessary to pass
in the external cluster IP, and/or set up an external IP for the
LoadBalancer Service.

If neither of these are available, just use port-forwarding as for
the other tests. That doesn't actually test the Service types, since
connections are forwarded to the clusterIP. But the tests can be
run in automation when the external networking is not available.

The helm charts already do this, it is a change for the kubectl/yaml
examples, which have been using NodePort. NodePort has been
unnecessary since we've automated testing by using port-forward to
the Service. This brings the two different deployment methods more
in line.

We will add tests for LoadBalancer and NodePort Services.

The docs are now even more out of sync with the actual example/test
code, since they still reference the NodePort type.

Previously the status was only updated when the sync to implement an
Ingress was successful. This will update the status due to changes
in addresses (IPs or hosts) assigned to the Service.

Also, the Service info sources for Ingress loadBalancer status depend
on the Service type, mostly following the nginx ingress implementation.

The addresses for this array are taken from the public names and/or
IPs in the spec for Service(s) that expose the Ingress. These are
identified as:

- in the same namespace as the admin Service
- have the label viking.uplex.de/svc=public
- have the same selectors as the admin Service
- type is one of ClusterIP, NodePort or LoadBalancer

The label viking.uplex.de/svc is only required if the Ingress status
update is required. For example to use a tool like ArgoCD, or if
the cloud provider requires it.

Set the label in the Service template for the viking-service chart.

No longer needed since we've set the Pods to ready regardless of
whether an Ingress has been configured.