add 4.4.0-rc.2 to candidate

[vfreex]

No description provided.

[LalatenduMohanty]

I am not able to verify that 4.3 -> 4.4 update hangs on ClusterOperatorDegraded, NodeInstallerDegraded, RevisionControllerDegraded, TargetConfigControllerDegraded -> https://bugzilla.redhat.com/show_bug.cgi?id=1812584 (This is in verified state) is fixed in this build.

Also following bugs are not fixed in the build.

• cluster-etcd-operator should not scale when upgrading from 4.3 to 4.4 -> https://bugzilla.redhat.com/show_bug.cgi?id=1813512
• "You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert" on FIPS enabled cluster after upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1810418

So we are fine introducing this build in candidate but we need to block the edge to this.

[wking]

So we are fine introducing this build in candidate but we need to block the edge to this.

New discussion: we don't care about gating update edges in candidate channels, because the idea is to allow folks to experiment. Remove all blocked edges that only impact candidate channels.

/lgtm

[LalatenduMohanty]

/lgtm

[wking]

Needs a rebase around #127.

[sdodson]

/lgtm

[sdodson]

Rebased.

[jwforres]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jwforres, LalatenduMohanty, sdodson, vfreex, wking

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:

• channels/OWNERS [jwforres]

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