Add openshift-ingress-canary to remote-libvirt-e2e

[andymcc]

For 4.7+ the ingress operator will be degraded if it can not resolve
openshift-ingress-canary.apps.domain - we should add this to the
hardcoded list in the virsh network, as well as in the hostAliases.

[r4f4]

/lgtm

[jaypoulz]

/lgtm Good catch!

[jaypoulz]

/assign @crawford

[jaypoulz]

/test core-dry

[bbguimaraes]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andymcc, bbguimaraes, jaypoulz, r4f4

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/templates/openshift/installer/OWNERS [bbguimaraes]

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]

@andymcc: Updated the following 5 configmaps:

• prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster api.ci using the following files:
  • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
• prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster app.ci using the following files:
  • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
• prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster build01 using the following files:
  • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
• prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster build02 using the following files:
  • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
• prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster vsphere using the following files:
  • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml

Details

In response to this:

For 4.7+ the ingress operator will be degraded if it can not resolve
openshift-ingress-canary.apps.domain - we should add this to the
hardcoded list in the virsh network, as well as in the hostAliases.

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.