Fix: fix security context for Vector

[FahadKhalid210]

Issue: #6

[regisb]

This will cause the vector containers to run as root, right? I'd rather avoid this if we can. All containers should run in unprivileged mode. Is there any way to grant access to the container logs without promoting Vector to root?

[FahadKhalid210]

@regisb yes, currently it runs as root user. There is no user(id: 1000) in vector image that's why it missing the tracking logs data. I've checked in tutor-aspects like how they manage it but they also remove that part.
Ref: https://github.com/openedx/tutor-contrib-aspects/pull/209/files

[regisb]

There is no user(id: 1000) in vector image that's why it missing the tracking logs data.

Indeed, in dev/local mode vector runs as a privileged user, whereas other services run as user: "1000:1000". This explains why vector works in dev/local but not on Kubernetes. I see no other solution to resolve this issue, so we should accept that vector runs as a privileged container.

[regisb]

Thanks for the fix! I agree with the approach, but we must be more explicit towards end users in the changelog.

[DawoudSheraz]

Approving to unblock this. But do create a followup issue to see if we can create a user during build time that can be used as value of removed settings.