Thank you for your good work, it takes a lot of effort to harden the security aspect of things.
I found out that docker's SYS_ADMIN does not actually mean anything in Kubernetes. See here, and according to the docs here and specs here, all of them seem to also support this unofficial document.
And if you add CAP_SYS_ADMIN instead of SYS_ADMIN, it will block allowPrivilegeEscalation to be set to true. Also, when CAP_SYS_ADMIN is added, Collabora forks and works. Therefore, it would be great if you can include this change in the heml charts.
Thank you for your good work, it takes a lot of effort to harden the security aspect of things.
I found out that docker's
SYS_ADMIN
does not actually mean anything in Kubernetes. See here, and according to the docs here and specs here, all of them seem to also support this unofficial document.And if you add
CAP_SYS_ADMIN
instead ofSYS_ADMIN
, it will blockallowPrivilegeEscalation
to be set to true. Also, whenCAP_SYS_ADMIN
is added, Collabora forks and works. Therefore, it would be great if you can include this change in the heml charts.