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

[Jira:"kube-apiserver"] monitor test apiserver-incluster-availability collection

Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 38.46%.

Sample (being evaluated) Release: 4.20
Start Time: 2025-08-07T00:00:00Z
End Time: 2025-08-14T16:00:00Z
Success Rate: 38.46%
Successes: 5
Failures: 8
Flakes: 0
Base (historical) Release: 4.19
Start Time: 2025-05-18T00:00:00Z
End Time: 2025-06-17T23:59:59Z
Success Rate: 100.00%
Successes: 103
Failures: 0
Flakes: 0

View the test details report for additional context.

Hits a few tests, doesn't fail every run, but often. Unfortunately whatever is catching the panic is swallowing the trace, we can't see exactly where it's happening offhand.

Filed by: dgoodwin@redhat.com

There seem to be a few problems in here affecting three tests. The additional tests to the above are:

[Jira:"kube-apiserver"] monitor test apiserver-incluster-availability setup
[Jira:"kube-apiserver"] monitor test apiserver-incluster-availability cleanup

Setup is failing I think due to:

time="2025-08-18T10:04:26Z" level=error msg="failed to get hypershift management cluster config and namespace" error="both the HYPERSHIFT_MANAGEMENT_CLUSTER_KUBECONFIG and the HYPERSHIFT_MANAGEMENT_CLUSTER_NAMESPACE env var must be set"

Plus some otherwise bad code assuming it's executing within ginko tests, which is not the case here. (in NewHypershiftManagementCLI)

The cleanup failure seems simpler.