Publish FAR to Stable Channel

[razo7]

Getting ready to new release and with the workload deletion logic FAR can be subscribed published to the stable channel.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[razo7]

/test 4.13-openshift-e2e

[razo7]

I think the channel in CI should be updated as well (OO_CHANNEL: candidate).

[slintes]

I think the channel in CI should be updated as well (OO_CHANNEL: candidate).

yes!

Also: we do not "subscribe" here, we "publish" in a channel 🙂

[razo7]

CI will pass only after openshift/release#41861 is merged

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: razo7, slintes

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 [razo7,slintes]

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

[razo7]

/retest

[razo7]

/retest

[razo7]

/retest

[slintes]

/retest

[razo7]

/retest

[razo7]

I am unsure why VA was not been deleted on the first e2e test on OCP 4.12. I am pretty confident that it is unrelated to the PR change.
/retest

[razo7]

/retest