Switch cloud-event-proxy e2e-aws to use ClusterPool (cluster_claim)#74797
Conversation
|
Hi @yaronh12. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
|
/pj-rehearse pull-ci-redhat-cne-cloud-event-proxy-main-e2e-aws |
|
@edcdavid: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/cc @edcdavid |
|
/pj-rehearse |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
edcdavid
left a comment
There was a problem hiding this comment.
Looks good to me but don't we need to also change the 4.x release directories for config/job
right! I'll do that |
|
/pj-rehearse |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-redhat-cne-cloud-event-proxy-release-4.21-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.22-e2e-aws |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-redhat-cne-cloud-event-proxy-release-4.20-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.14-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.15-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.16-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.17-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.18-e2e-aws pull-ci-redhat-cne-cloud-event-proxy-release-4.19-e2e-aws |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edcdavid, josephdrichard, jzding, liangxia, yaronh12 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse ack |
|
@yaronh12: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
…penshift#74797) * changed cloud-event-proxy e2e-aws from ipi to cluster-claim from openshift-ci * Added cep to cluster claim allowlisy * Regenerate presubmits for Hive cluster claim support * Switch cloud-event-proxy e2e-aws to Hive cluster claims across all releases * restored 4.10 ci to old method * revert 4.9 and 4.11 configs to IPI * revert 4.9 and 4.11 configs to IPI
The
e2e-awspresubmit job forredhat-cne/cloud-event-proxycurrently takes 1-2 hours to complete. The vast majority of that time is spent on the IPI cluster installation step (ipi-install-install), which takes ~48 minutes .The actual test phase (
hack/deploy_test.sh deploy+make functests) only takes ~2.5 minutes.Solution
Replace the full IPI cluster installation (
openshift-e2e-awsworkflow) with a pre-warmed cluster from OpenShift CI'sClusterPoolusingcluster_claimand thegeneric-claimworkflow.Related