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

Supply exceptions json in helm chart #393

Open
Pionerd opened this issue Feb 13, 2024 · 1 comment
Open

Supply exceptions json in helm chart #393

Pionerd opened this issue Feb 13, 2024 · 1 comment
Assignees

Comments

@Pionerd
Copy link

Pionerd commented Feb 13, 2024

Overview

Currently it does not seem possible to easily supply an exceptions JSON file to Kubescape when using the helm chart.

Problem

We would like to run Kubescape scans using the Operator while taking into account the exceptions. Currently there is no way to supply the json to the Operator.

Solution

I would like to see this possibility, or pointers how we can already do it. In that case I will create a PR to the helm chart to make it easier for others.

Alternatives

Entering the exceptions in the ARMO portal is not desired. Running Kubescape manually with the --exceptions flag is not desired.

Additional context

N/A

@dwertent
Copy link
Contributor

Hi @Pionerd,
This is something we have been working on for a while now. In the end, the exceptions will be handled in CRD objects to facilitate integrations. We have already started working on it and have submitted a few related PRs in the respective projects. However, we haven't been able to merge them yet.
Currently, the most effective way to set exceptions is through third-party adaptors like ARMO.

@matthyx matthyx moved this to Triage in Kubescaping Aug 18, 2024
@matthyx matthyx moved this from Triage to Feature in Kubescaping Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Feature
Development

No branches or pull requests

3 participants