fix: set security context for init intercept

[smehboub]

Fixes: #3804

[thallgren]

I suspect that this might be a breaking change. I would prefer to see an option to inject the securityContext as a whole from the helm-chart, similar to how we handle the resources for the init-container. We already have this in the chart's values.yaml:

agent:
  logLevel:
  resources: { }
  initResources: { }

Adding a

  initSecurityContext: {}

here, inject its JSON as an environment variable unless empty in the deployment.yaml, and then add the logic needed to use that environment variable, would make the securityContext fully configurable.

[thallgren]

Looks promising, but it removes the default securityContext with the NET_ADMIN capability. That's still a breaking change. The default must remain.

[smehboub]

Looks promising, but it removes the default securityContext with the NET_ADMIN capability. That's still a breaking change. The default must remain.

Hello @thallgren
Thank you very very much for the review.

[thallgren]

Looks great. Thanks for providing this!