Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[馃檹]Support discovery of dockerconfig secrets #1467

Open
mmerrill3 opened this issue Mar 11, 2024 · 0 comments
Open

[馃檹]Support discovery of dockerconfig secrets #1467

mmerrill3 opened this issue Mar 11, 2024 · 0 comments

Comments

@mmerrill3
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant