Feature: support to skip the validation of indirectly related resources involved in webhook mutating#4473
Conversation
03d5e48 to
daa0864
Compare
…es involved in webhook mutating Signed-off-by: jiuyu <guotongyu.gty@alibaba-inc.com>
daa0864 to
6ae1975
Compare
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheyang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test fluid-e2e |
|
/retest |
|
@Syspretor: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |



For performance and stability considerations, we introduced a caching layer in the design of the webhook. However, this leads to cache update delays in scenarios involving large-scale concurrent resource creation, resulting in resource validation failures, even though the resource state in the API server is already correct. This PR provides an annotation in the pod, allowing for the specification of certain pods where, during the webhook mutation process, the validation of indirectly related resources can be skipped. This approach helps to both avoid issues with resource state updates due to caching delays in large-scale concurrent scenarios and optimize the performance of mutations.