SCC for deploying docs to Openshift via Helm

Docs
1

Hi there,

I’m trying to deploy docs via the Onlyoffice Kubernetes Documentation and I would like to enquire about the two approaches.

What are the implications of using either method - docs-components vs nonroot-v2? Would there be a difference in the UID, GID, fsGroup configurations in the docs Helm chart?

Thanks.

2

Forgot to add - I was under the impression that the docs image was generated by UID 101, meaning you would need your Openshift pods to be run on UID 101, so how would nonroot-v2 help with anything as an alternative approach?

3

Hello @johntan757575

First of all, please note that cluster deployment requires special license for Document Server. If you are planning to run Document Server in a cluster, please reach out to sales@onlyoffice.com to discuss the details.

Basically, there is little difference in both approaches. By default Document Server runs from user 101, in case you do not want to grant rights for that user, nonroot-v2 should be used as an alternative approach.

Other queries must be reviewed separately, taking into consideration your environment and goals. For that I recommend contacting Sales Department to discuss further troubleshooting.

4

Hi Constantine,

I’ve actually reached out to sales regarding a quote, and would like to discuss further about the deployment of Onlyoffice to Openshift, as I’m running into several issues.