securityContext to knative-eventing

[scr112]

Hi, we're using your operator and found that in knative-eventing, Security-context is defined in eventing-core, and there's no way to change it through the operator.
Can you suggest anything?
Our information security has blocked root launches.

[houshengbo]

Can you describe what you would like to configure for the resources in eventing-core and how you want to configure them?

[jouve]

Hi,

I would interested with this too.

This relates to using knative with restricted pod security context (explicit runAsNonRoot, runAsUser, etc).
Most components are already compliant, but request-reply for example is not.
I think it would be best if knative-operator defined the fields by default in the embedded manifests. That way, there is no need to change the CRD/operator.

On a similar topic, I would also be interested to run the components with hostUsers=false that is now GA in 1.36.

ref:

• https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
• https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.