WIP: Block 4.2 -> 4.3.10 for Azure clusters

[wking]

We don't know why we started seeing this in 4.3.10, and installer defaults for Azure CPU capacity haven't changed between 4.2 and 4.3, but I'm pushing this up as a mock up of what "block this edge for some types of clusters" might look like.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wking
To complete the pull request process, please assign crawford
You can assign the PR to them by writing /assign @crawford in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• OWNERS [wking]
• blocked-edges/OWNERS

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

[wking]

/hold

Just to be extra sure that we don't land this mock up ;).

[openshift-ci-robot]

@wking: PR needs rebase.

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

[wking]

I've translated from this brief sketch (which didn't generate much interest) into a formal enhancement with openshift/enhancements#426.

/close

[openshift-ci-robot]

@wking: Closed this PR.

Details

In response to this:

I've translated from this brief sketch (which didn't generate much interest) into a formal enhancement with openshift/enhancements#426.

/close

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.

[wking]

#1056 should be the real deal :)