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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: remove Trivys own ns from the exclude list #752

Merged
merged 1 commit into from
Dec 5, 2022

Conversation

dirien
Copy link
Contributor

@dirien dirien commented Dec 2, 2022

Signed-off-by: Engin Diri engin@pulumi.com

Description

This PR removes Trivys own NS from the OPERATOR_EXCLUDE_NAMESPACES list.

Related issues

Remove this section if you don't have related PRs.

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

Signed-off-by: Engin Diri <engin@pulumi.com>
@chen-keinan
Copy link
Contributor

@dirien lgtm 🚀 holding merge until releasing v0.8.0

@chen-keinan chen-keinan self-requested a review December 4, 2022 07:48
@chen-keinan chen-keinan merged commit d98930c into aquasecurity:main Dec 5, 2022
@dirien dirien deleted the trivy-ns branch December 26, 2022 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression: Trivy Operator can not scan its own namespace
2 participants