Helm: Added various configuration options for the Tetragon Operator Deployment

[PhilipSchmid]

I have added multiple configuration options for the Tetragon Operator Deployment, which are often crucial for enterprise-grade deployments that need to happen within certain security boundaries.

According to my current understanding, this should not break anything for existing users. The only chance I see a breakage happen is when somebody already configured .Values.serviceAccount.name in the past. The thing is, this value was never considered, and the SA was simply named {{ .Release.Name }} or {{ .Release.Name }}-operator-service-account. With this change, it would suddenly be considered for the actual SA naming.

• helm: Added extraVolumes support for the Tetragon Operator
• helm: Added extra labels for the Tetragon Operator Deployment and Pods
• helm: Added configurable annotations for the Tetragon Operator Deployment and Pods
• helm: Made the placement of Tetragon Operator Deployment Pods configurable
• helm: Made update strategy configurable for the Tetragon Operator Deployment
• helm: Made resource configurable for the Tetragon Operator Deployment
• helm: Added pod/container securityContext to the Tetragon Operator Deployment
• helm: Added priorityClassName to the Tetragon Operator Deployment
• helm: Added imagePullSecret to the Tetragon Operator Deployment

Fixes: #1761

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	2aa5b16
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/6569a005c8357900082dd59d
😎 Deploy Preview	https://deploy-preview-1817--tetragon.netlify.app/docs/reference/helm-chart
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[lambdanis]

This is great, thank you.

I left one comment about labels configuration, but more like food for thought.

[lambdanis]

@PhilipSchmid I see the CI is failing:

• The generated docs are not up to date - ./install/kubernetes/test.sh should do the trick
• The commit messages are too long

Could you fix these?

[PhilipSchmid]

@lambdanis I just shortened the commit messages and checked that the .test.sh script no longer generates new changes. Unfortunately, the CI is now even more unhappy with this PR 😆.

[lambdanis]

Oh dear, it looks like some Quay hiccup maybe? The CI failures definitely don't looks related to the changes. I'll rerun.

[lambdanis]

checked that the .test.sh script no longer generates new changes

Ok, I run on your branch and it looks like the trailing space here is the problem. I suppose your editor is removing trailing spaces automatically? If you could remove this space from the script, then it should pass :) (a bit surprising that nobody hit it before tbh)

[lambdanis]

After some flakes the CI finally passes, so I'm merging it, thank you @PhilipSchmid!