Bug 1872080: Add Dockerfile.rhel to match build configuration in ocp-build-data

[elmiko]

This change adds a new Dockerfile.rhel file to control builds that
target rhel. It is inspired by the automatically generated patches which
ensure that build files match what is in the
ocp-build-data repository
used for producing release artifacts.

After this change merges, the configuration files in
https://github.com/openshift/release/tree/master/ci-operator/config/openshift/cluster-api-provider-baremetal
and
https://github.com/openshift/ocp-build-data/blob/openshift-4.6/images/baremetal-machine-controller.yml
should be updated with the new dockerfile path.

[openshift-ci-robot]

@elmiko: This pull request references Bugzilla bug 1872080, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1872080: Add Dockerfile.rhel to match build configuration in ocp-build-data

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.

[elmiko]

this patch is intended to replace #99, the reason i am proposing a new dockerfile is to help enable our community(OKD) users to continue to build these components while not disrupting the rhel-based builds needed for our releases.

[dhellmann]

It's a shame that there's no easy way to specify variations like that in a single Dockerfile.

@elmiko I assume the community you're referring to is OKD rather than metal3 (since metal3 has a different implementation of the provider these days)?

/approve

[elmiko]

It's a shame that there's no easy way to specify variations like that in a single Dockerfile.

++

@elmiko I assume the community you're referring to is OKD rather than metal3 (since metal3 has a different implementation of the provider these days)?

yea, sorry for the ambiguity. i'll update, thanks =)

[michaelgugino]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, elmiko, michaelgugino

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:

• OWNERS [dhellmann]

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]

@elmiko: Some pull requests linked via external trackers have merged:

• operator-framework/operator-registry#426

The following pull requests linked via external trackers have not merged:

• operator-framework/operator-marketplace#331 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

Bugzilla bug 1872080 has not been moved to the MODIFIED state.

In response to this:

Bug 1872080: Add Dockerfile.rhel to match build configuration in ocp-build-data

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.

[elmiko]

adding a reference to the dependent PR, openshift-eng/ocp-build-data#636