2.2 KiB
2.2 KiB
v1alpha1_match_resources_t
Properties
| Name | Type | Description | Notes |
|---|---|---|---|
| exclude_resource_rules | list_t * | ExcludeResourceRules describes what operations on what resources/subresources the policy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded) | [optional] |
| match_policy | char * | matchPolicy defines how the "MatchResources" list is used to match incoming requests. Allowed values are "Exact" or "Equivalent". - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but "rules" only included `apiGroups:["apps"], apiVersions:["v1"], resources: ["deployments"]`, the admission policy does not consider requests to apps/v1beta1 or extensions/v1beta1 API groups. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and "rules" only included `apiGroups:["apps"], apiVersions:["v1"], resources: ["deployments"]`, the admission policy does consider requests made to apps/v1beta1 or extensions/v1beta1 API groups. The API server translates the request to a matched resource API if necessary. Defaults to "Equivalent" | [optional] |
| namespace_selector | v1_label_selector_t * | [optional] | |
| object_selector | v1_label_selector_t * | [optional] | |
| resource_rules | list_t * | ResourceRules describes what operations on what resources/subresources the admission policy matches. The policy cares about an operation if it matches any Rule. | [optional] |