Comment 2 for bug 1929234

Seeing what looks like a similar issue on aws here: https://solutions.qa.canonical.com/testruns/testRun/33ed9e4f-5d3b-4a62-b34b-b54642df3862

test_dns_provider fails, but on the backend it looks like it's actually an issue getting a lock on the nginx pod:

E0528 13:15:59.858909 7 leaderelection.go:325] error retrieving resource lock ingress-nginx-kubernetes-worker/ingress-controller-leader-nginx: Get "https://10.152.183.1:443/api/v1/namespaces/ingress-nginx-kubernetes-worker/configmaps/ingress-controller-leader-nginx": dial tcp 10.152.183.1:443: connect: connection refused