AggregatedAPIDown alert threshold set back to 85%

[raptorsun]

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

This pull request reverts a patch to version 4.8 that mitigates a problem when upgrading monitoring components from 4.7 to 4.8: AggregatedAPIDown is triggered due to a long period of unavailability of prometheus adapter. Both deployments are offline at the same time during the upgrade.

After integrating these 2 PRs(PR1, PR2) into 4.8 release, Prometheus Adapter is able to keep itself always available during the upgrade process. We can set back the alert threshold to its default value 85%.

[raptorsun]

/retest

[openshift-ci]

@raptorsun: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-single-node	66086e9	link	/test e2e-aws-single-node

Full PR test history. Your PR dashboard.

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.

[simonpasquier]

/lgtm
/hold
@dgrisonnet can you have a second look? Once it merges, we need to carefully monitor the CI logs to verify that the AggregatedAPIDown alert doesn't start firing again for 4.9 jobs.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raptorsun, simonpasquier

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 [raptorsun,simonpasquier]

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

[dgrisonnet]

Looks good from my side.
I will monitor the CI, but the alert shouldn't fire anymore because of non highly available aggregated APIs since they should all have been made HA in 4.8, so we shouldn't have any disruption during a 4.8 to 4.9 upgrade.

/unhold

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.