add debugging for aggregator flake

[liggitt]

capture current state of the APIService and extension server pod for output in failure cases

xref #63622

NONE

[jennybuckley]

Thanks! this is really helpful, that test doesn't really output very much which is making it pretty hard to debug.

I opened #64587 to capture the state of the APIService, extension server pods, and those pod logs in failures cases

We might also need to get the logs from the pod that is running the sample-apiserver even if it doesn't fail. From the logs I saw it looked like it wasn't failing, just taking a long time (or forever) to start the server. Not sure how possible that is to do, though.

[liggitt]

We might also need to get the logs from the pod that is running the sample-apiserver even if it doesn't fail. From the logs I saw it looked like it wasn't failing, just taking a long time (or forever) to start the server. Not sure how possible that is to do, though.

that would cause a timeout failure, which this should capture

[jennybuckley]

ah I see you were saying if the test failed, not if the pod failed. My mistake. Are you going to just keep retesting this until it flakes?

[liggitt]

Are you going to just keep retesting this until it flakes?

since it only kicks in when the test fails, I'd probably merge this to get data from CI runs

[liggitt]

/retest

[liggitt]

/assign @jennybuckley @cheftako

[liggitt]

/retest

[jennybuckley]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jennybuckley, liggitt

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:

• test/OWNERS [liggitt]

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

[liggitt]

/milestone v1.11
/kind bug
/priority important-soon
/status approved-for-milestone
/sig api-machinery

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process

@cheftako @jennybuckley @liggitt

Pull Request Labels

• sig/api-machinery: Pull Request will be escalated to these SIGs if needed.
• priority/important-soon: Escalate to the pull request owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.
• kind/bug: Fixes a bug discovered during the current release.

Help

• Additional instructions
• Commands for setting labels

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here.