That is, if they are neither viking services, nor an IngressBackend
for any Ingress with the viking Ingress class.

This reduces the Event noise for Services that have nothing to do
with viking.

All of the tests that deploy the service generate secrets for the
test.

Forgot it in the previous commit.

This test also intermittently gets 503 responses immediately after
the config is loaded.

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.