Record events when QuotaReservation and Admition take place.

[trasc]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Record different events when QuotaReservation and Admition take place.

Which issue(s) this PR fixes:

Fixes #1392

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Added event for QuotaReserved and fixed event for Admitted to trigger when admission checks complete

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	30fa933
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/657b15e69ffee30009485801

[trasc]

/hold For #1428 to merge, it uses that same test event recorder.

[trasc]

/retest

[trasc]

/unhold

[trasc]

/cc @alculquicondor

[alculquicondor]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, trasc

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 [alculquicondor]

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

[mimowo]

LGTM overall, just a couple of nits

[mimowo]

/label tide/merge-method-squash
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 14df760793c2eae53a56cd575d8dbf937ad066d1

[alculquicondor]

/kind bug
/remove-kind feature
/cherry-pick release-0.5
Because the existing events say "admitted", when it actually refers to quota reservation.

/release-note-edit

Added event for QuotaReserved and fixed event for Admitted to trigger when admission checks complete

[k8s-infra-cherrypick-robot]

@alculquicondor: once the present PR merges, I will cherry-pick it on top of release-0.5 in a new PR and assign it to you.

In response to this:

/kind bug
/remove-kind feature
/cherry-pick release-0.5
Because the existing events say "admitted", when it actually refers to quota reservation.

/release-note-edit

Added event for QuotaReserved and fixed event for Admitted to trigger when admission checks complete

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.

[alculquicondor]

/retest
(due to flaky test)

[k8s-infra-cherrypick-robot]

@alculquicondor: #1436 failed to apply on top of branch "release-0.5":

Applying: Use different events for QuotaReservation and Admission
Using index info to reconstruct a base tree...
M	pkg/constants/constants.go
M	pkg/controller/core/workload_controller.go
M	pkg/scheduler/scheduler.go
M	pkg/scheduler/scheduler_test.go
M	pkg/util/testing/client.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/util/testing/client.go
CONFLICT (content): Merge conflict in pkg/util/testing/client.go
Auto-merging pkg/scheduler/scheduler_test.go
Auto-merging pkg/scheduler/scheduler.go
Auto-merging pkg/controller/core/workload_controller.go
Auto-merging pkg/constants/constants.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use different events for QuotaReservation and Admission
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/kind bug
/remove-kind feature
/cherry-pick release-0.5
Because the existing events say "admitted", when it actually refers to quota reservation.

/release-note-edit

Added event for QuotaReserved and fixed event for Admitted to trigger when admission checks complete

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.

[alculquicondor]

/reopen
@trasc please prepare a cherry-pick for release-0.5

[k8s-ci-robot]

@alculquicondor: Failed to re-open PR: state cannot be changed. The pull request cannot be reopened.

In response to this:

/reopen
@trasc please prepare a cherry-pick for release-0.5

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.