crowdsecurity
set securityContext's from values
I actually needed #90 , but since it hasn't had any activity since over a year, and is making multiple changes (that IMHO should be split into different PR's) at once, I've created this simple change that gives users the flexibility to overwrite the securityContext definitions, while at the same time not breaking any existing deployments.
@dmaes: 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}
@dmaes: 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.
