add appsec in crowdsec chart #189
Conversation
|
@he2ss: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.
DetailsI 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. |
|
@he2ss: There are no area labels on this PR. You can add as many areas as you see fit.
DetailsI 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. |
|
/kind feature |
github-actions
bot
added
kind/feature
|
any news on this? |
| - name: COLLECTIONS | ||
| value: "crowdsecurity/appsec-virtual-patching" | ||
|
|
||
| # This allows the LAPI pod to register and communicate with the appsec pod |
There was a problem hiding this comment.
Add to readme they should not change ${REGISTRATION_TOKEN} as it will break things
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 : crowdsecurity/crowdsec#3202
⚠️ Do not merge before new crowdsec release including this PR