Add a delay in the verify script for the BackendConfig test.

The test intermittently gets 503 responses immediately after the
configuration becomes valid. Possibly because the controller is
still updating the config, or the probe settings do not set the
backend as healthy on startup.

This is a workaround until the cause is clarified.

examples/backend-config/verify.sh

-../hello/verify.sh
\ No newline at end of file

examples/backend-config/verify.sh

+#! /bin/bash -ex
+
+MYDIR=$(dirname ${BASH_SOURCE[0]})
+source ${MYDIR}/../../test/utils.sh
+
+LOCALPORT=${LOCALPORT:-8888}
+
+wait_until_ready app=varnish-ingress
+wait_until_configured app=varnish-ingress
+
+# XXX intermittent 503 responses immediately after configured is true
+sleep 5
+
+kubectl port-forward svc/varnish-ingress ${LOCALPORT}:80 >/dev/null &
+trap 'kill $(jobs -p)' EXIT
+wait_for_port ${LOCALPORT}
+
+varnishtest ${TESTOPTS} -Dlocalport=${LOCALPORT} cafe.vtc