Will there be a replacement functionality for kind/resource for k8s scans?

[coffeemakingtoaster]

Description

The recent update to version 0.51 updated the UX for Kubernetes scanning. While I do agree that the new approach is more intuitive and less confusing, I was wondering if the kind/resource functionality will be reimplemented.

As I understand it, it is currently not possible to target resources with a specific name. This capability was available with the old approach and can be quite useful, especially when working with branches in a CI environment.

For example, previously, it was possible to achieve this by executing the command:

trivy k8s deployments/<branchname>

However, with the new UX, I don't see how to perform the same action.

Once again, I'm a fan of the recent update! I just wanted to see if there are any plans to address this particular edge case. 🚀

Target

Kubernetes

Scanner

None

[chen-keinan]

@coffeemakingtoaster currently there are no plans to re-introduce kind/resource scanning

[itaysk]

we considered that use case (scanning a single resource) rare for Trivy users. given that it didn't align with the new UX we decided to omit it. But if we see that people ask for it (for example by commenting on this discussion), we can consider re-thinking how it can fit in the new UX.