cluster-api-provider-baremetal: Reflect upstream repository rename.

[russellb]

The upstream org for this repo moved from metalkube/ to metal3-io/.

The follow openshift PR depends on this update to the canonical go
repo: openshift/cluster-api-provider-baremetal#26

[openshift-ci-robot]

@russellb: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/cluster-api-provider-baremetal/master/govet	c69ce5a	link	/test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.2/govet	c69ce5a	link	/test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-baremetal/release-4.3/govet	c69ce5a	link	/test pj-rehearse
ci/prow/pj-rehearse	c69ce5a	link	/test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[dhellmann]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, russellb

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

The pull request process is described here

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-api-provider-baremetal/OWNERS [dhellmann,russellb]

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]

@russellb: Updated the following 6 configmaps:

• ci-operator-master-configs configmap in namespace ci-stg using the following files:
  • key openshift-cluster-api-provider-baremetal-master.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-master.yaml
• ci-operator-4.2-configs configmap in namespace ci using the following files:
  • key openshift-cluster-api-provider-baremetal-release-4.2.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.2.yaml
• ci-operator-4.2-configs configmap in namespace ci-stg using the following files:
  • key openshift-cluster-api-provider-baremetal-release-4.2.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.2.yaml
• ci-operator-4.3-configs configmap in namespace ci using the following files:
  • key openshift-cluster-api-provider-baremetal-release-4.3.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.3.yaml
• ci-operator-4.3-configs configmap in namespace ci-stg using the following files:
  • key openshift-cluster-api-provider-baremetal-release-4.3.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-release-4.3.yaml
• ci-operator-master-configs configmap in namespace ci using the following files:
  • key openshift-cluster-api-provider-baremetal-master.yaml using file ci-operator/config/openshift/cluster-api-provider-baremetal/openshift-cluster-api-provider-baremetal-master.yaml

In response to this:

The upstream org for this repo moved from metalkube/ to metal3-io/.

The follow openshift PR depends on this update to the canonical go
repo: openshift/cluster-api-provider-baremetal#26

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.