Skip to content

Latest commit

 

History

History
15 lines (11 loc) · 2.12 KB

V1beta1RuleWithOperations.md

File metadata and controls

15 lines (11 loc) · 2.12 KB

V1beta1RuleWithOperations

RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.

Properties

Name Type Description Notes
api_groups list[str] APIGroups is the API groups the resources belong to. '' is all groups. If '' is present, the length of the slice must be one. Required. [optional]
api_versions list[str] APIVersions is the API versions the resources belong to. '' is all versions. If '' is present, the length of the slice must be one. Required. [optional]
operations list[str] Operations is the operations the admission hook cares about - CREATE, UPDATE, or * for all operations. If '*' is present, the length of the slice must be one. Required. [optional]
resources list[str] Resources is a list of resources this rule applies to. For example: 'pods' means pods. 'pods/log' means the log subresource of pods. '' means all resources, but not subresources. 'pods/' means all subresources of pods. '/scale' means all scale subresources. '/*' means all resources and their subresources. If wildcard is present, the validation rule will ensure resources do not overlap with each other. Depending on the enclosing object, subresources might not be allowed. Required. [optional]
scope str scope specifies the scope of this rule. Valid values are "Cluster", "Namespaced", and "" "Cluster" means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. "Namespaced" means that only namespaced resources will match this rule. "" means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is "*". [optional]

[Back to Model list] [Back to API list] [Back to README]