Gabe Alford

Hello, We don't support modification of the the securityContext as every securitycontext has to be tested internally. We also don't support setting seccomp policies as not only do they not...

Closing this as the supported securityContexts have been added in #263

> That worked @carlosmmatos , see (somewhat masked) result here: > > ``` > { > "access_token": "secret stuff", > "expires_in": 1799, > "token_type": "bearer" > } > ``` >...

Yeah totally does.... especially as that part was written before eBPF was officially supported in the container image.

The usage of helm parameters is generally the appropriate and preferred approach to handling this.

Hello, Please make sure that you are using the correct sensor image as the sensor image you are using in the new chart won't work because it is the sidecar...

`/opt/CrowdStrike/falconstore` should not be a directory and shouldn't have permissions 755. I would probably suggest cleaning up `/opt/CrowdStrike` by removing it entirely, and then redeploying. The `falcon-daemonset-init` takes care of...

@MattWeatherford this is because 24.04 is currently unsupported. See https://falcon.crowdstrike.com/documentation/page/edd7717e/falcon-sensor-for-linux-system-requirements

Hello, Currently, having FalconAPI configured and set is required for IAR functionality.

Hey @siggimoo. Checkout the https://github.com/CrowdStrike/falcon-operator/blob/main/docs/developer_guide.md . The project typically sticks to the versions recommended/supported through the operator-sdk.