Support for multi-ingress environments

[sivanov-nuodb]

Issue

If the test job is killed and HAProxy teardown doesn't execute, the IngressClass resource (which is cluster-scoped) will be left behind. This will cause all subsequent executions of the test to fail with the following message:

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "haproxy" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "haproxy-ooimr1": current value is "haproxy-mgyoxp"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "testkubernetesingress-5czgy7": current value is "testkubernetesingress-s0uufa"

Changes

Added support for multi-ingress environments.

For more information, see https://github.com/haproxytech/helm-charts/tree/main/kubernetes-ingress#installing-in-multi-ingress-environment.