This was a remnant of earlier versions when the Pods were set to not
Ready when there is no Ingress to implement. No the Pods are always
ready, but we set the "configured" endpoint to respond with non-200
when nothing is defined.

However, if an Ingress had been defined previously, then deleted,
the http/https endpoints still responded as for the previous config.
This was semantically incorrect, and also meant that the VCL config
remained defined indefinitely. Now it becomes unlabeled, so it can
go cold and then be discarded.