SRVKP-3342: Add pipelines cluster pool

[divyansh42]

This PR adds the cluster pool and its required configurations. A follow-up PR will be done to modify the cluster claim test configurations of the different components.

[openshift-ci-robot]

@divyansh42: This pull request references SRVKP-3342 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:

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.

[divyansh42]

@savitaashture @jkandasa @khrm Can I please get review on this PR. Thanks.

[openshift-ci-robot]

@divyansh42: This pull request references SRVKP-3342 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:

This PR adds the cluster pool and its required configurations. A follow-up PR will be done to modify the cluster claim test configurations of the different components.

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.

[khrm]

/lgtm

[savitaashture]

• Can we add one more cluster pool yaml for 4.16 as well because Pipeline supported on 4.16 also

[divyansh42]

• Can we add one more cluster pool yaml for 4.16 as well because Pipeline supported on 4.16 also

Sure, will add for 4.16 as well.

[savitaashture]

1.15 OSP supported from 4.14 onwards as per the component matrix http://dashboard.apps.cicd.ospqa.com/product/componentmatrix/
should we add clusterpool for only those versions ??
wdyt @khrm @jkandasa @vdemeester ?

[divyansh42]

1.15 OSP supported from 4.14 onwards as per the component matrix http://dashboard.apps.cicd.ospqa.com/product/componentmatrix/ should we add clusterpool for only those versions ?? wdyt @khrm @jkandasa @vdemeester ?

I think that probably makes sense.
When I was adding cluster pools for all the versions, I was under the impression that we would have test jobs for all other versions as well. But while modifying cluster pool in those test jobs, I only see 4.14 related tests.

[divyansh42]

@savitaashture Removed 4.12 and 4.13 cluster pool. PTAL.

[khrm]

/approve

[savitaashture]

Thank you @divyansh42 🎉

[divyansh42]

As per the comment from the CI bot I am tagging @droslean for the approval. @droslean could you please approve the PR? Thank you.
/assign @droslean

[khrm]

/lgtm

[deepsm007]

you can remove status

[deepsm007]

same as above

[divyansh42]

Done, thanks for the review @deepsm007 🙂

[deepsm007]

same as above

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@divyansh42: no rehearsable tests are affected by this change

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@divyansh42: 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.

[deepsm007]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, divyansh42, khrm, savitaashture, vdemeester

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:

• clusters/hosted-mgmt/hive/pools/OWNERS [deepsm007]

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