OKD-40: Use a default RHEL_VERSION when the build argument is not specified

[aleskandro]

In OKD, we will always want to keep the "RHEL_VERSION" set by the base CentOS stream image used to build the dtk image.

[Prashanth684]

/test okd-scos-images

[openshift-ci]

@aleskandro: all tests passed!

Full PR test history. Your PR dashboard.

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

[Prashanth684]

/cc @ybettan

[LorbusChris]

/lgtm
/assign @bthurber

[LorbusChris]

/label acknowledge-critical-fixes-only

[Prashanth684]

@bthurber i know you laid out your concerns here: #145 (comment) , but we still feel this will be useful for the community if they want to build and test custom modules. As for the question of support, this will be supported through the community.

[bthurber]

@bthurber i know you laid out your concerns here: #145 (comment) , but we still feel this will be useful for the community if they want to build and test custom modules. As for the question of support, this will be supported through the community.

I am OK with adding it for OKD as-long-as there aren't any support expectations around it. Of course we can provide guidance and comment as needed but we won't be doing any formal QE or e2e testing in this space.

[Prashanth684]

@bthurber i know you laid out your concerns here: #145 (comment) , but we still feel this will be useful for the community if they want to build and test custom modules. As for the question of support, this will be supported through the community.

I am OK with adding it for OKD as-long-as there aren't any support expectations around it. Of course we can provide guidance and comment as needed but we won't be doing any formal QE or e2e testing in this space.

There is no expectation of RedHat support for OKD - so yes, that is not a problem.

[openshift-ci-robot]

@aleskandro: This pull request references OKD-40 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

In OKD, we will always want to keep the "RHEL_VERSION" set by the base CentOS stream image used to build the dtk image.

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 openshift-eng/jira-lifecycle-plugin repository.

[ausil]

@bthurber i know you laid out your concerns here: #145 (comment) , but we still feel this will be useful for the community if they want to build and test custom modules. As for the question of support, this will be supported through the community.

I am OK with adding it for OKD as-long-as there aren't any support expectations around it. Of course we can provide guidance and comment as needed but we won't be doing any formal QE or e2e testing in this space.

Could you please approve it so it can be merged? This is the last thing holding up OKD being built on CentOS Stream

[bthurber]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleskandro, bthurber

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 [bthurber]

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

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build driver-toolkit-container-v4.16.0-202405161711.p0.g465152a.assembly.stream.el9 for distgit driver-toolkit.
All builds following this will include this PR.