Configurable serviceAccountName for agent deployment

[arthurzenika]

We're deploying CrowdSec with this helm chart and would like to give the deployment a serviceAccountName of a serviceAccount (that already exists) which gives it access to SQS/SNS/S3... This doesn't seem configurable in the helm chart. Would you welcome a contribution adding this feature ? (serviceAccountName would be optionnal of course)

[github-actions]

@arthurzenika: Thanks for opening an issue, it is currently awaiting triage.

If you haven't already, please provide the following information:

• kind : bug, enhancementor documentation
• area : agent, appsec, configuration, cscli, local-api

In the meantime, you can:

1. Check Crowdsec Documentation to see if your issue can be self resolved.
2. You can also join our Discord.
3. Check Releases to make sure your agent is on the latest version.

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]

@arthurzenika: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

• /kind bug
• /kind documentation
• /kind enhancement

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.

[arthurzenika]

/kind enhancement

[arthurzenika]

/area agent