OCPNODE-1705: blocked-edges/4.13.*-PerformanceProfilesCPUQuota: Declare new risk

[wking]

The PromQL approach is similar to what we used in c641333 (#2552), except:

• I'm using the PerformanceProfiles resource.
• I'm using apiserver_storage_objects instead of cluster:usage:resources:sum, to cut out one lossy layer of indirection.

Generated by writing the 4.13.0 declaration by hand, and then copying out to other 4.13 releases with:

$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.13' | jq -r '.nodes[].version' | grep '^4[.]13[.]' | grep -v '^4[.]13[.]0$' | while read V; do sed "s/4[.]13[.]0/${V}/g" blocked-edges/4.13.0-PerformanceProfilesCPUQuota.yaml > "blocked-edges/${V}-PerformanceProfilesCPUQuota.yaml"; done
$ git add blocked-edges/4.13.*PerformanceProfilesCPUQuota.yaml

[openshift-ci-robot]

@wking: This pull request references OCPNODE-1705 which is a valid jira issue.

Details

In response to this:

The PromQL approach is similar to what we used in c641333 (#2552), except:

• I'm using the PerformanceProfiles resource.
• I'm using apiserver_storage_objects instead of cluster:usage:resources:sum, to cut out one lossy layer of indirection.

Generated by writing the 4.13.0 declaration by hand, and then copying out to other 4.13 releases with:

$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.13' | jq -r '.nodes[].version' | grep '^4[.]13[.]' | grep -v '^4[.]13[.]0$' | while read V; do sed "s/4[.]13[.]0/${V}/g" blocked-edges/4.13.0-PerformanceProfilesCPUQuota.yaml > "blocked-edges/${V}-PerformanceProfilesCPUQuota.yaml"; done
$ git add blocked-edges/4.13.*PerformanceProfilesCPUQuota.yaml

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]

Testing out the PromQL, here's a cluster without any PerformanceProfiles, with the expected 0:

And here's simulating the presence of the exposing resource by substituting in clusterversions.config.openshift.io, with the expected 1:

And here's simulating apiserver_storage_objects scraping failing by substituting apiserver_storage_objectsX, with the expected No datapoints found:

[petr-muller]

/test e2e

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, 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:

• OWNERS [petr-muller,wking]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 40c8dc8 and 2 for PR HEAD b573872 in total

[petr-muller]

openshift-release-dev/ocp-release with layer_digest sha256:a85a707d9f1238d8b214379958ac7de19eb2b5aa631057eb07bdf1b7bdc3eff9: request failed with status 500 Internal Server Error

sadge quay

[wking]

I'm ok not waiting on Quay.

/override ci/prow/e2e

[openshift-ci]

@wking: Overrode contexts on behalf of wking: ci/prow/e2e

Details

In response to this:

I'm ok not waiting on Quay.

/override ci/prow/e2e

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.

[openshift-ci]

@wking: 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/test-infra repository. I understand the commands that are listed here.