Ingress Operator: Add optional e2e-azure-operator job

[sgreene570]

Adds an optional, non-blocking e2e-azure-operator job
to exercise the Ingress Operator's e2e test suite
on Azure clusters. The Ingress Operator has a similair
optional job for GCP (See #15823),
and a mandatory job for AWS. A PR against the Ingress Operator's master
branch should have the ability to run against AWS, GCP, or Azure, since
the operator has platform specific code for all of those platforms.

[sgreene570]

cc @openshift/openshift-team-network-edge

[Miciah]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, sgreene570

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-ingress-operator/OWNERS [Miciah,sgreene570]
• ci-operator/jobs/openshift/cluster-ingress-operator/OWNERS [Miciah,sgreene570]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@sgreene570: Updated the following 3 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-cluster-ingress-operator-master.yaml using file ci-operator/config/openshift/cluster-ingress-operator/openshift-cluster-ingress-operator-master.yaml
• job-config-master configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-cluster-ingress-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-ingress-operator/openshift-cluster-ingress-operator-master-presubmits.yaml
• job-config-master configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-cluster-ingress-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-ingress-operator/openshift-cluster-ingress-operator-master-presubmits.yaml

Details

In response to this:

Adds an optional, non-blocking e2e-azure-operator job
to exercise the Ingress Operator's e2e test suite
on Azure clusters. The Ingress Operator has a similair
optional job for GCP (See #15823),
and a mandatory job for AWS. A PR against the Ingress Operator's master
branch should have the ability to run against AWS, GCP, or Azure, since
the operator has platform specific code for all of those platforms.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.