Add release branch to the image push trigger

[andreyvelich]

Since we decided to use release- branch, we need to update the image push trigger in our CI.

/assign @kubeflow/wg-training-leads

[andreyvelich]

cc @Electronic-Waste

[Electronic-Waste]

/lgtm

Nice job @andreyvelich ! And just a question. Shall we add the release branch to the UT/e2e tests trigger? Is it safe enough not to test the release branch?

[andreyvelich]

Shall we add the release branch to the UT/e2e tests trigger? Is it safe enough not to test the release branch?

I guess, we run our UT and E2E on all branches already, isn't @Electronic-Waste ?
https://github.com/kubeflow/training-operator/blob/master/.github/workflows/integration-tests.yaml#L68

[coveralls]

Pull Request Test Coverage Report for Build 12654542847

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 12643949527:	0.0%
Covered Lines:	85
Relevant Lines:	85

---

💛 - Coveralls

[Electronic-Waste]

@andreyvelich Thanks for the clarification. LGTM!

[andreyvelich]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich, Electronic-Waste

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

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

[andreyvelich]

/cherry-pick release-1.9

[google-oss-robot]

@andreyvelich: new pull request created: #2377

In response to this:

/cherry-pick release-1.9

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/test-infra repository.