Open
Description
Describe the user need
In order to properly configure the snyk-monitor secret with the right dockerconfig secrets, I need to dynamically look up the secrets that are used in an enterprise, which are different for an environment of hundreds of clusters, for each cluster.
Instead, why can't this application just use the same secrets that the workload is already using? Why do I need to configure this information again?
Describe expected behaviour
When prompted to scan a workload, kubernetes-monitor just uses the same secrets that the workload is configured to use.
Additional context
Add any other context or screenshots about the feature request here.