You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many policies target the Pod resource, however, creating this resource in a direct way is considered a Kubernetes anti-pattern. Most of the time, Pod resources are created by higher-order resources like Deployment, DaemonSet, CronJob, ReplicaSet,...
Currently, our SDKs provide APIs that allow the policy author to make his policy work also against the most common Kubernetes resources that have Pod objects specified inside of them.
However, this is extra work that has to be done on a per-policy basis.
On the other hand, Kyverno has the concept of auto-gen rules which makes the whole process simpler.
It would be useful to create a RFC that describes how we could create a Kubewarden feature similar to the auto-gen rules of Kyverno.
The text was updated successfully, but these errors were encountered:
flavio
changed the title
RFC: how to make Pod specific policies work against high order resources
RFC: how to make Pod specific policies work against higher-order resources
Aug 7, 2023
Many policies target the Pod resource, however, creating this resource in a direct way is considered a Kubernetes anti-pattern. Most of the time, Pod resources are created by higher-order resources like Deployment, DaemonSet, CronJob, ReplicaSet,...
Currently, our SDKs provide APIs that allow the policy author to make his policy work also against the most common Kubernetes resources that have Pod objects specified inside of them.
However, this is extra work that has to be done on a per-policy basis.
On the other hand, Kyverno has the concept of auto-gen rules which makes the whole process simpler.
It would be useful to create a RFC that describes how we could create a Kubewarden feature similar to the auto-gen rules of Kyverno.
The text was updated successfully, but these errors were encountered: