fix(kubernetes): temporary solution for updated k8s python client
This commit is contained in:
parent
07d6fe7442
commit
9129813244
1478 changed files with 422354 additions and 2 deletions
14
kubernetes/docs/V1FlowSchemaSpec.md
Normal file
14
kubernetes/docs/V1FlowSchemaSpec.md
Normal file
|
@ -0,0 +1,14 @@
|
|||
# V1FlowSchemaSpec
|
||||
|
||||
FlowSchemaSpec describes how the FlowSchema's specification looks like.
|
||||
## Properties
|
||||
Name | Type | Description | Notes
|
||||
------------ | ------------- | ------------- | -------------
|
||||
**distinguisher_method** | [**V1FlowDistinguisherMethod**](V1FlowDistinguisherMethod.md) | | [optional]
|
||||
**matching_precedence** | **int** | `matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence. Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default. | [optional]
|
||||
**priority_level_configuration** | [**V1PriorityLevelConfigurationReference**](V1PriorityLevelConfigurationReference.md) | |
|
||||
**rules** | [**list[V1PolicyRulesWithSubjects]**](V1PolicyRulesWithSubjects.md) | `rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema. | [optional]
|
||||
|
||||
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
|
||||
|
||||
|
Reference in a new issue