Security Context is Not Set in Init Container

[dan-fernandes]

BlueAPI's .Values.securityContext is only applied to the main container, not the init container. (I suspect) this means that the init and main containers can run as different users, root or non root, etc.

This seems to be causing issues, such as scratch dependencies downloaded by the init container not being modifiable by the main container (see #1363). It also makes some issues unreproducible due to not being able to choose the UID of the init container (see #1308 which could only be reproduced if the init container ran as non-1000).

Propagating the security context is easy, but I'm nervous that this may have unforeseen consequences.

Acceptance Criteria

• Init container's security context can be set via .Values