Open mosinnik opened 4 months ago
@mosinnik
It related to https://github.com/longhorn/longhorn/issues/8088 with workarounds.
I think it's Loghorn bug with mount as root with super privileges instead of use disk
group. As what I see that bug was already fixed by this PR https://github.com/longhorn/longhorn-engine/pull/1043. Please try to update this component
So we need to able to setup securityContext for pods in operator manifest or remove runAsNonRoot: true
In most cases it's securityContext configuration allows you to run the YDB cluster correctly with respecting the security restrictions. Probably it'll be good enhancement if we found enough cases where it will be useful. In this case it's not bug of ydb-operator
Default storage cfg.
On storage pod on stating got:
Inside pod ydb run as ydb user but device mapped mounted for root without additional rights for ydb user:
It related to https://github.com/longhorn/longhorn/issues/8088 with workarounds. So we need to able to setup securityContext for pods in operator manifest or remove
runAsNonRoot: true
operator 0.5.16 kube: 1.27.4