DPTP-4751: Migrate o/release postsubmit jobs on app.ci to core-ci

[liangxia]

The dependencies of secrets and serviceaccounts have been synced to core-ci cluster in earlier PRs.

Verified job config-change-trigger and vsphere02-apply still works on cluster core-ci.

job branch-ci-openshift-release-main-release-controller-annotate can not verify this way, because we switch from using serviceAccountName to mounted secret which contains kubeconfig, so that we can run the job on cluster core-ci to operator resources on cluster app.ci ( using serviceAccount means if the job runs on cluster core-ci, then it operator resources on cluster core-ci, which is not expected ).

[openshift-ci-robot]

@liangxia: This pull request references DPTP-4751 which is a valid jira issue.

Details

In response to this:

The dependencies of secrets and serviceaccounts have been synced to core-ci cluster in earlier PRs.

Verified job config-change-trigger and vsphere02-apply still works on cluster core-ci.

job branch-ci-openshift-release-main-release-controller-annotate can not verify this way, because we switch from using serviceAccountName to mounted secret which contains kubeconfig, so that we can run on cluster core-ci to operator resources on cluster app.ci

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.

[openshift-ci-robot]

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

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci-robot]

@liangxia: This pull request references DPTP-4751 which is a valid jira issue.

Details

In response to this:

The dependencies of secrets and serviceaccounts have been synced to core-ci cluster in earlier PRs.

Verified job config-change-trigger and vsphere02-apply still works on cluster core-ci.

job branch-ci-openshift-release-main-release-controller-annotate can not verify this way, because we switch from using serviceAccountName to mounted secret which contains kubeconfig, so that we can run the job on cluster core-ci to operator resources on cluster app.ci ( using serviceAccount means if the job runs on cluster core-ci, then it operator resources on cluster core-ci, which is not expected ).

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.

[openshift-ci]

@liangxia: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[liangxia]

/cc @openshift/test-platform

[danilo-gemoli]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danilo-gemoli, liangxia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/jobs/openshift/release/OWNERS [danilo-gemoli,liangxia]
• core-services/sanitize-prow-jobs/OWNERS [danilo-gemoli,liangxia]

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