(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

install should succeed: overall

Significant regression detected.
Fishers Exact probability of a regression: 99.99%.
Test pass rate dropped from 98.93% to 93.83%.

Sample (being evaluated) Release: 4.20
Start Time: 2025-07-25T00:00:00Z
End Time: 2025-08-01T16:00:00Z
Success Rate: 93.83%
Successes: 76
Failures: 5
Flakes: 0

Base (historical) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-10-01T00:00:00Z
Success Rate: 98.93%
Successes: 371
Failures: 4
Flakes: 0

View the test details report for additional context.

Looks to be this job which is permafailing and today has run three times for some reason, which was enough to trigger a regression on gcp.

The job needs to either be fixed, or needs to be categorized so it will not be included in component readiness. Setting the job explicitly to candidate status could be a way to do that, here is an example: https://github.com/openshift/sippy/pull/2514/files
Setting Procedure=custom-dns might be a good idea as well for the future. (again in ocp.go)

Just note that nothing will remember to remove that once the job is fixed, and it will forever be excluded from CR and thus not monitored for regressions.