crowdsecurity
add appsec in crowdsec chart
fix #170
Adding the ability to configure and enable the Appsec Component.
In the Kubernetes environment, to be able to handle inband and out of band, we deployed an extra pod with an agent responsible only to receive bouncers appsec traffic.
Depends on : https://github.com/crowdsecurity/crowdsec/pull/3202 :warning: Do not merge before new crowdsec release including this PR
@he2ss: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.
/kind feature/kind enhancement/kind fix/kind chore/kind dependencies
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@he2ss: There are no area labels on this PR. You can add as many areas as you see fit.
/area agent/area local-api/area cscli/area security/area configuration
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.
