feat: add event recorder event for lws controller

[googs1025]

What type of PR is this?

/kind feature

What this PR does / why we need it

• add event for lws controller

I have only added an event recorder for the LWS controller and did not add any events for the pod controller. This decision was made because I believe that users will only be interested in events generated by the LWS controller and not those generated by the pod controller.
If there is a need to add events for the pod controller, please let me know and I will add them accordingly.

Which issue(s) this PR fixes

refer to: #100

Special notes for your reviewer

Does this PR introduce a user-facing change?

None

[k8s-ci-robot]

Hi @googs1025. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[liurupeng]

/ok-to-test

[liurupeng]

/lgtm

[googs1025]

/retest

[googs1025]

/test pull-lws-test-integration-main

[googs1025]

/test pull-lws-test-integration-main

[googs1025]

@liurupeng @kerthcet When I was running the CI, I noticed that errors were occurring, which was not expected. It seems like there might be some issues in the code. I feel like adding the event recorder alone shouldn't cause this error.

[googs1025]

Wait for a while and check again. There haven't been any error messages.

[liurupeng]

/approve
/lgtm

[liurupeng]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: googs1025, liurupeng

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

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

[googs1025]

/retest

[kerthcet]

/retest

Please don't retest if you have a flaky, will lead to the code baseline unstable.

[kerthcet]

I don't think these events make sense to the system, event usually generated for state transitions, or specific reasons for diagnosis, not logging.

Please revert them. The only one makes sense to me is the createHeadlessService failed event, which is an important signal.

No need to created a new file to container the constants, they're not shared, located at this file is enough.

[googs1025]

ok, i fix it right now

[kerthcet]

Discussed offline, hope to have a event to tell us that the rolling update is failed but there's no specific signal indicates the rolling update is failed. So maybe keep the same as sts right now.(Sts doesn't have a event to report that the rolling update is failed as well.)

Fix me if not.