Category
Internal refactors/changes
Describe the feature you'd like to request
There have been discussions in upstream of having a "unified selector", which would use CEL syntax/AST instead of the k8s-specific labelSelector query syntax, and the (by design) untyped/arbitrary query syntax of fieldSelectors (which don't have e.g. in semantics IIRC).
We should follow this development and align with whatever selectors we expose here. The authorizer have to parse the selector into structs that Cedar can understand.
Describe alternatives you've considered
Additional context
No response
Is this something that you'd be interested in working on?
Category
Internal refactors/changes
Describe the feature you'd like to request
There have been discussions in upstream of having a "unified selector", which would use CEL syntax/AST instead of the k8s-specific labelSelector query syntax, and the (by design) untyped/arbitrary query syntax of fieldSelectors (which don't have e.g. in semantics IIRC).
We should follow this development and align with whatever selectors we expose here. The authorizer have to parse the selector into structs that Cedar can understand.
Describe alternatives you've considered
Additional context
No response
Is this something that you'd be interested in working on?