[Enhancement] Consider adding resource matching rules to the KRM-KCL Spec

[Peefy]

Background

In the current version of the KRM KCL specification, users need to repeatedly write and filter certain types of resource codes such as service and deployments, and consider adding resource filtering declarations to further reduce the required code volume, such as the following form.

resourceRules:
 - apiGroups:   ["apps"]
   apiVersions: ["v1"]
   resources:   ["deployments"]

Reference

• Kubernetes Validating Admission Policy: https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/

[satyazzz123]

Hello @peefy can I work on this issue?

[satyazzz123]

Hello @Peefy I had a question

In the current version of the KRM KCL specification, users need to repeatedly write and filter certain types of resource codes such as service and deployments

How do we currently write deployments and services inside KCL , can I see some examples of where there is a typical usage of resource code for deployments and services

[Peefy]

Hello @Peefy I had a question

In the current version of the KRM KCL specification, users need to repeatedly write and filter certain types of resource codes such as service and deployments

How do we currently write deployments and services inside KCL , can I see some examples of where there is a typical usage of resource code for deployments and services

Here's documents https://kcl-lang.io/docs/user_docs/guides/working-with-k8s/overview

In fact, what this issue wants to do is to filter these fields through configuration when there is a series of resource inputs on the resource transformer. https://github.com/kcl-lang/krm-kcl/blob/main/pkg/edit/transformer.go#L38

Expanding it based on existing transformer interfaces is a better way.

[shruti2522]

Would be happy to take this one, @Peefy

[Peefy]

Thank you! @shruti2522