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
Is your feature request related to a problem? Please describe.
Currently, when using cnspec for k8s, if I specify "--discover pods", not all pods of my cluster are detected.
If I want to access information of individual pods (eg node or status), I can only do so for the subset of pods that are being respected by "--discover pods".
Describe the solution you'd like
It would be great to have a "--discover" option, eg "pods-all", to discover each pod on the cluster.
Describe alternatives you've considered
None available, if I need to access pod-specific information of pods, created by another object (Deployment, Daemonset,..).
Additional context
We want to be able to build pod based policies, without having to specify the policy for each type of pod-creating asset type (Deployment, Daemonset,..).
Instead (or in addition) to having to write a policy for each k8s workload type, we can also have one generic policy for pods.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, when using cnspec for k8s, if I specify "--discover pods", not all pods of my cluster are detected.
If I want to access information of individual pods (eg node or status), I can only do so for the subset of pods that are being respected by "--discover pods".
Describe the solution you'd like
It would be great to have a "--discover" option, eg "pods-all", to discover each pod on the cluster.
Describe alternatives you've considered
None available, if I need to access pod-specific information of pods, created by another object (Deployment, Daemonset,..).
Additional context
We want to be able to build pod based policies, without having to specify the policy for each type of pod-creating asset type (Deployment, Daemonset,..).
Instead (or in addition) to having to write a policy for each k8s workload type, we can also have one generic policy for pods.
The text was updated successfully, but these errors were encountered: