Display input for KubeRay parameter and check for existence

[ChristianZaccaria]

Issue link

What changes have been made

Display KubeRay parameter in release workflow and check for the existence of the chosen KubeRay release.

Previously the KubeRay parameter was not displayed

Verification steps

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • Testing is not required for this change

[sutaakar]

Can you make sure that the step fails in case KubeRay version is not available?

[sutaakar]

@ChristianZaccaria Thinking about usage of Check if KubeRay release exists.
Should it be just informative or should it be considered as a prerequisite of the release?

[ChristianZaccaria]

@ChristianZaccaria Thinking about usage of Check if KubeRay release exists. Should it be just informative or should it be considered as a prerequisite of the release?

I think in this case we will always want to specify an existing version of KubeRay to ensure the compatibility matrix is updated to the correct version we have tested. Inputting a non existing version in the matrix could cause confusion. What do you think?

[sutaakar]

In such case it may be good to fail whole pipeline in case KubeRay version is not valid.
Can you adjust other steps to require this new step to pass first before being triggered?

[ChristianZaccaria]

I added that check now. I think we don't really require the check-kuberay-version to be triggered for instascale or codeflare-operator as the other components will need to pass first. Should I keep the check or remove them from instascale and CFO?

[sutaakar]

You can remove it from InstaScale and operator

[ChristianZaccaria]

Updated, I think it's good to go. Thanks Karel

[sutaakar]

One nitpick above,otherwise looks fine.

[ChristianZaccaria]

Thanks good catch!

[sutaakar]

Thanks

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sutaakar

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

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