Mutating webhook configs
Mutating Webhook Configs view#
In the Kubernetes context, MutatingAdmissionWebhooks allow you to customize and validate resources as they are introduced to a cluster. These webhooks enable you to modify and validate resources, ensuring they meet specific criteria when they are added to your cluster. See Kubernetes Documentation: Admission Controllers Reference for details.
The Mutating Webhook Configs table lists the cluster MutatingAdmissionWebhooks. You can click the list items and open the details panel with comprehensive information and various options. You can also search for a specific item using the Search input field.
You can resize and reorder the table columns. Drag the column border in the table header to change the width. To change the column position, drag its header left or right. Also, you can sort objects in ascending or descending order by clicking the header of a column and configure the column visibility. By default, the table consists of the following columns:
Note
The table content can be exported in the CSV file format.
| Column | Description |
|---|---|
| Name | Displays the name of each Mutating Admission Webhook. |
| Webhooks | Contains details about the webhook's configuration, such as server and client settings. |
| Age | Indicates how long the webhook has been in use. |
| More Actions |
Clicking on the button opens a drop-down list with the following actions:
|
Match conditions#
Each webhook entry can include CEL matchConditions that gate when the webhook is invoked. All match conditions inside a webhook entry must evaluate to true for the webhook to run.
Lens Desktop renders each match condition as a drawer item in the Match Conditions section of the webhook's detail panel. The condition name labels the drawer item, and the CEL expression is shown with theme-aware syntax highlighting using the same renderer as admission policies. See CEL syntax highlighting for the colour token reference.
Webhook match conditions can reference only the request-context variables object, oldObject, request, and authorizer. They do not support params, variables, or namespaceObject, because webhook configurations have no paramKind or composited variable mechanism.