HyperEvent needs a universal extraction capability.

[hnhbwlp]

Problem description

Currently, the extraction process in HyperEvent is customized for pod resources in operations. If users need to trace a new resource, they have to write code to add an extractor, which is quite costly.

What I expect

The extraction action in HyperEvent should be more universal and able to adapt to multiple resources.

What I want to do

• Perform request/response object diff operation for the audit logs of Update verbs, which requires a high-performance software.

• Establish a new Operation model to identify Patch and Update verb operations uniformly as JSON path format operations.

• Deserialize runtime.Object using a generic approach, referencing the method used by client-go to identify unknown Custom Resources (CR), to avoid the need to introduce the user's scheme when adding a new CR.

[hnhbwlp]

cc @linuzb