The following guide covers the installation process of the ‘ONLYOFFICE DocSpace’ into a Kubernetes cluster or OpenShift cluster.
- Requirements
- Deploy prerequisites
- Deploy ONLYOFFICE DocSpace
- Parameters
- Common parameters
- ONLYOFFICE DocSpace Application parameters
- ONLYOFFICE DocSpace Router Application additional parameters
- ONLYOFFICE DocSpace Doceditor Application additional parameters
- ONLYOFFICE DocSpace Login Application additional parameters
- ONLYOFFICE DocSpace Socket Application additional parameters
- ONLYOFFICE DocSpace Ssoauth Application additional parameters
- ONLYOFFICE DocSpace Proxy Frontend Application additional parameters
- ONLYOFFICE Docs parameters
- ONLYOFFICE DocSpace Ingress parameters
- ONLYOFFICE DocSpace Jobs parameters
- ONLYOFFICE DocSpace Elasticsearch parameters
- ONLYOFFICE DocSpace Test parameters
- Configuration and installation details
- ONLYOFFICE DocSpace installation test (optional)
- Kubernetes version no lower than 1.19+ or OpenShift version no lower than 3.11+
- A minimum of two hosts is required for the Kubernetes cluster
- Resources for the cluster hosts: 4 CPU \ 8 GB RAM min
- Kubectl is installed on the cluster management host. Read more on the installation of kubectl here
- Helm v3.15+ is installed on the cluster management host. Read more on the installation of Helm here
- If you use OpenShift, you can use both
ocandkubectlto manage deploy. - If the installation of components external to ‘ONLYOFFICE DocSpace’ is performed from Helm Chart in an OpenShift cluster, then it is recommended to install them from a user who has the
cluster-adminrole, in order to avoid possible problems with access rights. See this guide to add the necessary roles to the user.
Note: It may be required to apply SecurityContextConstraints policy when installing into OpenShift cluster, which adds permission to run containers from a user whose ID = 1000 and ID = 1001.
To do this, run the following commands:
$ oc apply -f https://raw.githubusercontent.com/ONLYOFFICE/Kubernetes-DocSpace/main/sources/scc/helm-components.yaml
$ oc adm policy add-scc-to-group scc-helm-components system:authenticated
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm repo add nfs-server-provisioner https://kubernetes-sigs.github.io/nfs-ganesha-server-and-external-provisioner
$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
$ helm repo add onlyoffice https://download.onlyoffice.com/charts/stable
$ helm repo updateNote: When installing NFS Server Provisioner, Storage Classes - NFS is created. When installing to an OpenShift cluster, the user must have a role that allows you to create Storage Classes in the cluster. Read more here.
$ helm install nfs-server nfs-server-provisioner/nfs-server-provisioner \
--set persistence.enabled=true \
--set "storageClass.mountOptions={vers=4,timeo=20}" \
--set persistence.storageClass=PERSISTENT_STORAGE_CLASS \
--set persistence.size=PERSISTENT_SIZE-
PERSISTENT_STORAGE_CLASSis a Persistent Storage Class available in your Kubernetes cluster. -
PERSISTENT_SIZEis the total size of all Persistent Storages for the nfs Persistent Storage Class. Must be at least the sum of the values of thepersistenceandopensearch.persistence.sizeparameters ifpersistence.storageClass=nfsandopensearch.persistence.storageClass=nfs. You can express the size as a plain integer with one of these suffixes:T,G,M,Ti,Gi,Mi. For example:19Gi.
See more details about installing NFS Server Provisioner via Helm here.
The PersistentVolume type to be used for PVC placement must support Access Mode ReadWriteMany.
Also, PersistentVolume must have as the owner the user from whom the ONLYOFFICE DocSpace will be started. By default it is onlyoffice (104:107).
To install MySQL to your cluster, run the following command:
$ helm install mysql -f https://raw.githubusercontent.com/ONLYOFFICE/Kubernetes-DocSpace/main/sources/mysql_values.yaml bitnami/mysql \
--set auth.database=docspace \
--set auth.username=onlyoffice_user \
--set primary.persistence.storageClass=PERSISTENT_STORAGE_CLASS \
--set primary.persistence.size=PERSISTENT_SIZE \
--set metrics.enabled=falseSee more details about installing MySQL via Helm here.
Here PERSISTENT_SIZE is a size for the Database persistent volume. For example: 8Gi.
To install RabbitMQ to your cluster, run the following command:
$ helm install rabbitmq bitnami/rabbitmq \
--set persistence.storageClass=PERSISTENT_STORAGE_CLASS \
--set metrics.enabled=falseSee more details about installing RabbitMQ via Helm here.
To install Redis to your cluster, run the following command:
$ helm install redis bitnami/redis \
--set architecture=standalone \
--set master.persistence.storageClass=PERSISTENT_STORAGE_CLASS \
--set metrics.enabled=falseSee more details about installing Redis via Helm here.
To install OpenSearch to your cluster, set the opensearch.enabled=true parameter when installing ONLYOFFICE DocSpace.
If you want to connect ONLYOFFICE DocSpace with an external OpenSearch instance, you need to specify the corresponding values in connections.elkSheme, connections.elkHost, connections.elkPort, connections.elkThreads parameters and define opensearch.enabled parameter as false.
NOTE: By default, an installation made specifically for Kubernetes is used. This is added as a Helm Subchart. See more details about installing ONLYOFFICE Docs in Kubernetes via Helm here. Depending on the type of your DocSpace license, add the suffix -de - Developer Edition or -ee Enterprise Edition in the parameters: docs.docservice.image.repository, docs.proxy.image.repository and docs.converter.image.repository for Docs. By default - Community version.
if you plan to use the already installed Onlyoffice Docs and it is deployed in the same cluster as ONLYOFFICE DocSpace is planned to be deployed, then specify the name of the service in the connections.documentServerHost parameter and set false in the docs.enabled parameter.
Also, specify the Namespace if the Docs is deployed in a different Namespace than ONLYOFFICE DocSpace is planned, for example, documentserver.ds:8888.
Also, in the connections.appUrlPortal parameter, specify the router service name of the ONLYOFFICE DocSpace and the Namespace in which ONLYOFFICE DocSpace will be deployed, for example, http://router.default:8092.
If Kubernetes-Docs is deployed externally, relative to the cluster in which ONLYOFFICE DocSpace is planned to be deployed, then you need to specify the external Docs address in the connections.documentServerUrlExternal parameter in the http(s)://<documentserver-address>/ format and set docs.enabled to false and in the connections.appUrlPortal parameter, specify the external address of the ONLYOFFICE DocSpace, for example, https://docspace.example.com.
Also, when using Kubernetes-Docs, installed not as a subchart, specify the DocSpace JWT parameters the same as in Docs in jwt.secret, jwt.header, etc.
To create a Secret containing configuration files for overriding default values and additional configuration files for ONLYOFFICE DocSpace, you need to run the following command:
$ kubectl create secret generic docspace-custom-config \
--from-file=./appsettings.test.json \
--from-file=./notify.test.jsonNote: Any name can be used instead of docspace-custom-config.
Note: The example above shows two configuration files. You can use as many as you want, as well as only one file.
Note: When using the test suffix in the file name, set the connections.envExtension parameter to test.
When installing ONLYOFFICE DocSpace, specify the extraConf.secretName=docspace-custom-config and extraConf.filename={appsettings.test.json,notify.test.json} parameters.
Note: If you need to add a configuration file after the ONLYOFFICE DocSpace is already installed, you need to execute step 8.1
and then run the helm upgrade [RELEASE_NAME] onlyoffice/docspace --set extraConf.secretName=docspace-custom-config --set "extraConf.filename={appsettings.test.json,notify.test.json}" --no-hooks command or
helm upgrade [RELEASE_NAME] -f ./values.yaml onlyoffice/docspace --no-hooks if the parameters are specified in the values.yaml file.
Note: It may be required to apply SecurityContextConstraints policy when installing into OpenShift cluster, which adds permission to run containers from a user whose ID = 104.
To do this, run the following commands:
$ oc apply -f https://raw.githubusercontent.com/ONLYOFFICE/Kubernetes-DocSpace/main/sources/scc/docspace-components.yaml
$ oc adm policy add-scc-to-group scc-docspace-components system:authenticated
Also, you must set the podSecurityContext.enabled parameter to true:
$ helm install [RELEASE_NAME] onlyoffice/docspace --set podSecurityContext.enabled=true
If you have a valid ONLYOFFICE DocSpace license, set the connections.installationType parameter to ENTERPRISE and install ONLYOFFICE Docspace
$ helm install [RELEASE_NAME] -f values.yaml onlyoffice/docspace --set connections.installationType=ENTERPRISEAt the wizard page during the first login please add your license using the corresponding field.
If you have initially installed Community version and plan to switch to Enterprise version using the corresponding license, please perform an update using connections.installationType=ENTERPRISE parameter, then add your license using the corresponding field in Payments section.
To install ONLYOFFICE DocSpace to your cluster, run the following command:
$ helm install [RELEASE_NAME] -f values.yaml onlyoffice/docspaceThe command deploys ONLYOFFICE DocSpace on the Kubernetes cluster in the default configuration. The [Parameters] section lists the parameters that can be configured during installation.
See helm install for command documentation.
To uninstall/delete the docspace deployment:
$ helm uninstall [RELEASE_NAME]The helm uninstall command removes all the Kubernetes components associated with the chart and deletes the release.
See helm uninstall for command documentation.
Note: If you have Elasticsearch installed, please read this section.
Note: When upgrading to version 3.0.0 from an earlier version, set the parameters docs.upgrade.job.enabled and docs.clearCache.job.enabled to false. When installing version 3.0.0 or upgrading from version 3.0.0 to a later version, these parameters should be set to true. Additionally, when upgrading to version 3.0.0 from an earlier version, set the parameter upgrade.job.docsInitDB.enabled to true. However, when installing version 3.0.0 or upgrading from version "3.0.0" to a later version, this parameter should be set to false.
It's necessary to set the parameters for updating. For example,
$ helm upgrade [RELEASE_NAME] onlyoffice/docspace \
--set images.tag=[tag]Note: also need to specify the parameters that were specified during installation
Or modify the values.yaml file and run the command:
$ helm upgrade [RELEASE_NAME] -f values.yaml onlyoffice/docspaceRunning the helm upgrade command runs a hook that cleans up the directory with libraries and then fills with new ones. This is needed when updating the version of ONLYOFFICE DocSpace. The default hook execution time is 300s.
The execution time can be changed using --timeout [time], for example:
$ helm upgrade [RELEASE_NAME] -f values.yaml onlyoffice/docspace --timeout 15mIf you want to update any parameter other than the version of the ONLYOFFICE DocSpace, then run the helm upgrade command without hooks, for example:
$ helm upgrade [RELEASE_NAME] onlyoffice/docspace --set jwt.enabled=false --no-hooksSee helm upgrade for command documentation.
To rollback updates, run the following command:
$ helm rollback [RELEASE_NAME]See helm rollback for command documentation.
| Parameter | Description | Default |
|---|---|---|
connections.envExtension |
Defines whether an environment will be used | `` |
connections.installationType |
Defines solution type | COMMUNITY |
connections.migrationType |
Defines migration type | STANDALONE |
connections.mysqlDatabaseMigration |
Enables database migration | false |
connections.mysqlHost |
The IP address or the name of the Database host | mysql |
connections.mysqlPort |
Database server port number | 3306 |
connections.mysqlDatabase |
Name of the Database the application will be connected with. The database must already exist | docspace |
connections.mysqlUser |
Database user | onlyoffice_user |
connections.mysqlPassword |
Database user password. If set to, it takes priority over the connections.mysqlExistingSecret |
"" |
connections.mysqlExistingSecret |
Name of existing secret to use for Database passwords. Must contain the key specified in connections.mysqlSecretKeyPassword |
mysql |
connections.mysqlSecretKeyPassword |
The name of the key that contains the Database user password. If you set a password in connections.mysqlPassword, a secret will be automatically created, the key name of which will be the value set here |
mysql-password |
connections.redisHost |
The IP address or the name of the Redis host. If Redis is deployed inside a k8s cluster, then you need to specify the FQDN name of the service | redis-master.default.svc.cluster.local |
connections.redisPort |
The Redis server port number | 6379 |
connections.redisUser |
The Redis user name | default |
connections.redisExistingSecret |
Name of existing secret to use for Redis password. Must contain the key specified in connections.redisSecretKeyName |
redis |
connections.redisSecretKeyName |
The name of the key that contains the Redis user password. If you set a password in connections.redisPassword, a secret will be automatically created, the key name of which will be the value set here |
redis-password |
connections.redisPassword |
The password set for the Redis account. If set to, it takes priority over the connections.redisExistingSecret |
"" |
connections.redisNoPass |
Defines whether to use a Redis auth without a password. If the connection to Redis server does not require a password, set the value to true |
false |
connections.brokerHost |
The IP address or the name of the Broker host | rabbitmq |
connections.brokerPort |
The port for the connection to Broker host | 5672 |
connections.brokerVhost |
The virtual host for the connection to Broker host | / |
connections.brokerUser |
The username for the Broker account | guest |
connections.brokerProto |
The protocol for the connection to Broker host | amqp |
connections.brokerUri |
A string containing the necessary connection parameters to Broker. If set to, it takes priority | "" |
connections.brokerExistingSecret |
The name of existing secret to use for Broker password. Must contain the key specified in connections.brokerSecretKeyName |
rabbitmq |
connections.brokerSecretKeyName |
The name of the key that contains the Broker user password. If you set a password in connections.brokerPassword, a secret will be automatically created, the key name of which will be the value set here |
rabbitmq-password |
connections.brokerPassword |
Broker user password. If set to, it takes priority over the connections.brokerExistingSecret |
"" |
connections.elkSheme |
The protocol for the connection to Opensearch | http |
connections.elkHost |
The IP address or the name of the Opensearch host | opensearch |
connections.elkPort |
The port for the connection to Opensearch | 9200 |
connections.elkThreads |
Number of threads in Opensearch | 1 |
connections.apiHost |
The name of the ONLYOFFICE DocSpace Api service | api |
connections.apiSystemHost |
The name of the ONLYOFFICE DocSpace Api System service | api-system |
connections.notifyHost |
The name of the ONLYOFFICE DocSpace Notify service | notify |
connections.studioNotifyHost |
The name of the ONLYOFFICE DocSpace Studio Notify service | studio-notify |
connections.socketHost |
The name of the ONLYOFFICE DocSpace Socket service | socket |
connections.peopleServerHost |
The name of the ONLYOFFICE DocSpace People Server service | people-server |
connections.filesHost |
The name of the ONLYOFFICE DocSpace Files service | files |
connections.filesServicesHost |
The name of the ONLYOFFICE DocSpace Files Services service | files-services |
connections.studioHost |
The name of the ONLYOFFICE DocSpace Studio service | studio |
connections.backupHost |
The name of the ONLYOFFICE DocSpace Backup service | backup |
connections.ssoauthHost |
The name of the ONLYOFFICE DocSpace SSO service | ssoauth |
connections.clearEventsHost |
The name of the ONLYOFFICE DocSpace Clear Events service | clear-events |
connections.doceditorHost |
The name of the ONLYOFFICE DocSpace Doceditor service | doceditor |
connections.backupBackgroundTasksHost |
The name of the ONLYOFFICE DocSpace Backup Background Tasks service | backup-background-tasks |
connections.loginHost |
The name of the ONLYOFFICE DocSpace Login service | login |
connections.healthchecksHost |
The name of the ONLYOFFICE DocSpace Healthchecks service | healthchecks |
connections.identityApiHost |
The name of the ONLYOFFICE DocSpace Identity API service | identity-api |
connections.identityAuthorizationHost |
The name of the ONLYOFFICE DocSpace Identity service | identity-authorization |
connections.documentServerHost |
The name of the Document Server service. Used when installing a local Document Server (by default docs.enabled=true) |
document-server |
connections.documentServerUrlExternal |
The address of the external Document Server. If set, the local Document Server will not be installed | "" |
connections.appUrlPortal |
URL for ONLYOFFICE DocSpace requests. By default, the name of the routing (Router) service and the port on which it accepts requests are used | http://router:8092 |
connections.appCoreBaseDomain |
The base domain on which the ONLYOFFICE DocSpace will be available | localhost |
connections.appCoreMachinekey.secretKey |
The secret key used in the ONLYOFFICE DocSpace | your_core_machinekey |
connections.appCoreMachinekey.existingSecret |
The name of an existing secret containing Core Machine Key. Must contain the APP_CORE_MACHINEKEY key. If not specified, a secret will be created with the value set in connections.appCoreMachinekey.secretKey |
"" |
connections.countWorkerConnections |
Defines the nginx config worker_connections directive for routing (Router) service | 1024 |
connections.nginxSnvsubstTemplateSuffix |
A suffix of template files for rendering nginx configs in routing (Router) service | .template |
connections.oauthOrigin |
The address of the OAUTH2 server | "" |
connections.appKnownNetworks |
Defines the address ranges of known networks to accept forwarded headers from for ONLYOFFICE DocSpace services. In particular, the networks in which the proxies that you are using in front of DocSpace services are located should be indicated here. Provide IP ranges using CIDR notation | 10.244.0.0/16 |
connections.oauthRedirectURL |
Address of the oauth authorization server | https://service.onlyoffice.com/oauth2.aspx |
namespaceOverride |
The name of the namespace in which ONLYOFFICE DocSpace will be deployed. If not set, the name will be taken from .Release.Namespace |
"" |
commonLabels |
Defines labels that will be additionally added to all the deployed resources. You can also use tpl as the value for the key |
{} |
commonAnnotations |
Defines annotations that will be additionally added to all the deployed resources. You can also use tpl as the value for the key. Some resources may override the values specified here with their own |
{} |
podAnnotations |
Map of annotations to add to the ONLYOFFICE DocSpace pods. Each Docspace application can override the values specified here with its own | rollme: "{{ randAlphaNum 5 | quote }}" |
serviceAccount.create |
Enable ServiceAccount creation | false |
serviceAccount.name |
Name of the ServiceAccount to be used. If not set and serviceAccount.create is true the name will be taken from .Release.Name or serviceAccount.create is false the name will be "default" |
"" |
serviceAccount.annotations |
Map of annotations to add to the ServiceAccount | {} |
serviceAccount.automountServiceAccountToken |
Enable auto mount of ServiceAccountToken on the serviceAccount created. Used only if serviceAccount.create is true |
true |
podSecurityContext.enabled |
Enable security context for the pods. If set to true, podSecurityContext is enabled for all resources describing the podTemplate. Individual values for docs and elasticsearch |
false |
podSecurityContext.fsGroup |
Defines the Group ID to which the owner and permissions for all files in volumes are changed when mounted in the ONLYOFFICE DocSpace application Pods | 107 |
containerSecurityContext.enabled |
Enable security context for containers in ONLYOFFICE DocSpace application pods. Individual values for docs and opensearch |
false |
nodeSelector |
Node labels for ONLYOFFICE DocSpace application pods assignment. Each ONLYOFFICE Docspace application can override the values specified here with its own | {} |
tolerations |
Tolerations for ONLYOFFICE DocSpace application pods assignment. Each ONLYOFFICE Docspace application can override the values specified here with its own | [] |
imagePullSecrets |
Container image registry secret name | "" |
images.tag |
Global image tag for all DocSpace applications. Does not apply to the Document Server, Elasticsearch and Proxy Frontend | 3.0.1 |
jwt.enabled |
Specifies the enabling the JSON Web Token validation by the DocSpace | true |
jwt.secret |
Defines the secret key to validate the JSON Web Token in the request to the DocSpace | jwt_secret |
jwt.header |
Defines the http header that will be used to send the JSON Web Token | AuthorizationJwt |
jwt.inBody |
Specifies the enabling the token validation in the request body to the ONLYOFFICE DocSpace | false |
jwt.existingSecret |
The name of an existing secret containing variables for jwt. If not specified, a secret named jwt will be created |
"" |
extraConf.secretName |
The name of the Secret containing the json files that override the default values and additional configuration files | "" |
extraConf.filename |
The name of the json files that contains custom values and name additional configuration files. Must be the same as the key name in extraConf.secretName. May contain multiple values |
appsettings.test.json |
log.level |
Defines the type and severity of a logged event | Warning |
debug.enabled |
Enable debug | false |
initContainers.checkDB.image.repository |
check-db initContainer image repository | onlyoffice/docs-utils |
initContainers.checkDB.image.tag |
check-db initContainer image tag. If set to, it takes priority over the images.tag |
8.2.2-1 |
initContainers.checkDB.image.pullPolicy |
check-db initContainer image pull policy | IfNotPresent |
initContainers.checkDB.resources.requests.memory |
The requested Memory for the check-db initContainer | 256Mi |
initContainers.checkDB.resources.requests.cpu |
The requested CPU for the check-db initContainer | 100m |
initContainers.checkDB.resources.limits.memory |
The Memory limits for the check-db initContainer | 1Gi |
initContainers.checkDB.resources.limits.cpu |
The CPU limits for the check-db initContainer | 1000m |
initContainers.waitStorage.image.repository |
app-wait-storage initContainer image repository | onlyoffice/docspace-wait-bin-share |
initContainers.waitStorage.image.tag |
app-wait-storage initContainer image tag. If set to, it takes priority over the images.tag |
"" |
initContainers.waitStorage.image.pullPolicy |
app-wait-storage initContainer image pull policy | IfNotPresent |
initContainers.waitStorage.resources.requests.memory |
The requested Memory for the app-wait-storage initContainer | 256Mi |
initContainers.waitStorage.resources.requests.cpu |
The requested CPU for the app-wait-storage initContainer | 100m |
initContainers.waitStorage.resources.limits.memory |
The Memory limits for the app-wait-storage initContainer | 1Gi |
initContainers.waitStorage.resources.limits.cpu |
The CPU limits for the app-wait-storage initContainer | 1000m |
initContainers.initStorage.image.repository |
app-init-storage initContainer image repository | onlyoffice/docspace-bin-share |
initContainers.initStorage.image.tag |
app-init-storage initContainer image tag. If set to, it takes priority over the images.tag |
"" |
initContainers.initStorage.image.pullPolicy |
app-init-storage initContainer image pull policy | IfNotPresent |
initContainers.initStorage.resources.requests.memory |
The requested Memory for the app-init-storage initContainer | 256Mi |
initContainers.initStorage.resources.requests.cpu |
The requested CPU for the app-init-storage initContainer | 100m |
initContainers.initStorage.resources.limits.memory |
The Memory limits for the app-init-storage initContainer | 2Gi |
initContainers.initStorage.resources.limits.cpu |
The CPU limits for the app-init-storage initContainer | 1000m |
initContainers.custom |
Defines custom containers that run before ONLYOFFICE DocSpace containers in a Pods. For example, a container that changes the owner of the PersistentVolume. For the Docs, Router, Opensearch and Proxy Frontend services, the corresponding individual parameters are used |
[] |
persistence.storageClass |
PVC Storage Class for ONLYOFFICE DocSpace data volume | nfs |
persistence.docspaceData.existingClaim |
The name of the existing PVC for storing files common to all services. If not specified, a PVC named "docspace-data" will be created | "" |
persistence.docspaceData.annotations |
Defines annotations that will be additionally added to common files PVC. If set to, it takes priority over the commonAnnotations |
{} |
persistence.docspaceData.size |
PVC Storage Request for common files volume | 8Gi |
persistence.filesData.existingClaim |
The name of the existing PVC for use in the Files service. If not specified, a PVC named "files-data" will be created | "" |
persistence.filesData.annotations |
Defines annotations that will be additionally added to Files PVC. If set to, it takes priority over the commonAnnotations |
{} |
persistence.filesData.size |
PVC Storage Request for Files volume | 2Gi |
persistence.peopleData.existingClaim |
The name of the existing PVC for use in the People Server service. If not specified, a PVC named "people-data" will be created | "" |
persistence.peopleData.annotations |
Defines annotations that will be additionally added to People Server PVC. If set to, it takes priority over the commonAnnotations |
{} |
persistence.peopleData.size |
PVC Storage Request for People Server volume | 2Gi |
persistence.routerLog.existingClaim |
The name of the existing PVC for storing Nginx logs of the Router service. If not specified, a PVC named "router-log" will be created | "" |
persistence.routerLog.annotations |
Defines annotations that will be additionally added to Nginx logs PVC. If set to, it takes priority over the commonAnnotations |
{} |
persistence.routerLog.size |
PVC Storage Request for Nginx logs volume | 5Gi |
podAntiAffinity.type |
Types of Pod antiaffinity. Allowed values: preferred or required |
preferred |
podAntiAffinity.topologyKey |
Node label key to match | kubernetes.io/hostname |
podAntiAffinity.weight |
Priority when selecting node. It is in the range from 1 to 100. Used only when podAntiAffinity.type=preferred |
100 |
| Parameter | Description | Default |
|---|---|---|
Application.enabled |
Enables Application installation. Individual values for identity.authorization and identity.api |
true |
Application.kind |
The controller used for deploy. Possible values are Deployment (default) or StatefulSet. Not used in docs and opensearch |
Deployment |
Application.annotations |
Defines annotations that will be additionally added to Application deploy. If set to, it takes priority over the commonAnnotations |
{} |
Application.replicaCount |
Number of "Application" replicas to deploy. Not used in docs and opensearch |
2 |
Application.updateStrategy.type |
"Application" update strategy type | RollingUpdate |
Application.updateStrategy.rollingUpdate.maxUnavailable |
Maximum number of "Application" Pods unavailable during the update process | 25% |
Application.updateStrategy.rollingUpdate.maxSurge |
Maximum number of "Application" Pods created over the desired number of Pods | 25% |
Application.podManagementPolicy |
The Application Pods scaling operations policy. Used if Application.kind is set to StatefulSet. Not used in docs and opensearch |
OrderedReady |
Application.podAnnotations |
Map of annotations to add to the "Application" pods. If set to, it takes priority over the podAnnotations |
{} |
Application.podSecurityContext.enabled |
Enable security context for the "Application" pods. If set to, it takes priority over the podSecurityContext |
false |
Application.customPodAntiAffinity |
Prohibiting the scheduling of Api System Pods relative to other Pods containing the specified labels on the same node | {} |
Application.podAffinity |
Defines Pod affinity rules for "Application" Pods scheduling by nodes relative to other Pods | {} |
Application.nodeAffinity |
Defines Node affinity rules for "Application" Pods scheduling by nodes | {} |
Application.nodeSelector |
Node labels for Api System pods assignment. If set to, it takes priority over the nodeSelector |
{} |
Application.tolerations |
Tolerations for Api System pods assignment. If set to, it takes priority over the tolerations |
[] |
Application.image.repository |
"Application" container image repository. Individual values for proxyFrontend, docs and opensearch |
onlyoffice/docspace-Application |
Application.image.tag |
"Application" container image tag. If set to, it takes priority over the images.tag. Individual values for proxyFrontend, docs and opensearch |
"" |
Application.image.pullPolicy |
"Application" container image pull policy | IfNotPresent |
Application.containerSecurityContext.enabled |
Enable security context for containers in "Application" pods. If set to, it takes priority over the containerSecurityContext |
false |
Application.lifecycleHooks |
Defines the Backup container lifecycle hooks. It is used to trigger events to run at certain points in a container's lifecycle | {} |
Application.containerPorts.app |
"Application" container port. Not used in router, login and proxyFrontend, identity.authorization and identity.api |
5050 |
Application.startupProbe.enabled |
Enable startupProbe for "Application" container | true |
Application.readinessProbe.enabled |
Enable readinessProbe for "Application" container | true |
Application.livenessProbe.enabled |
Enable livenessProbe for "Application" container | true |
Application.resources.requests |
The requested resources for the "Application" container | memory, cpu |
Application.resources.limits |
The resources limits for the "Application" container | memory, cpu |
- Application* Note: Since all available Applications have some identical parameters, a description for each of them has not been added to the table, but combined into one.
Instead of
Application, the parameter name should have the following values:files,peopleServer,router,healthchecks,apiSystem,api,backup,backupBackgroundTasks,clearEvents,doceditor,filesServices,login,notify,socket,ssoauth,studio,studioNotify,proxyFrontend,docs,opensearch,identity.authorizationandidentity.api.
| Parameter | Description | Default |
|---|---|---|
router.initContainers |
Defines containers that run before Router container in the Router pod | [] |
router.containerPorts.external |
Router container port | 8092 |
router.extraEnvVars |
An array with extra env variables for the Router container | [] |
router.extraConf.customInitScripts.configMap |
The name of the ConfigMap containing custom initialization scripts | "" |
router.extraConf.customInitScripts.fileName |
The names of scripts containing custom initialization scripts. Must be the same as the key names in router.extraConf.customInitScripts.configMap. May contain multiple values |
60-custom-init-scripts.sh |
router.extraConf.templates.configMap |
The name of the ConfigMap containing configuration file templates containing environment variables. The values of these variables will be substituted when the container is started | "" |
router.extraConf.templates.fileName |
The names of the configuration file templates containing environment variables. Must be the same as the key names in router.extraConf.templates.configMap. May contain multiple values |
10.example.conf.template |
router.extraConf.confd.configMap |
The name of the ConfigMap containing additional custom configuration files. These files will be map in the /etc/nginx/conf.d/ directory of the container |
"" |
router.extraConf.confd.fileName |
The names of the configuration files containing custom configuration files. Must be the same as the key names in router.extraConf.confd.configMap. May contain multiple values |
example.conf |
router.service.existing |
The name of an existing service for Router. If not set, a service named router will be created |
"" |
router.service.annotations |
Map of annotations to add to the Router service | {} |
router.service.port.external |
Router service port | 8092 |
router.service.type |
Router service type | ClusterIP |
router.service.sessionAffinity |
Session Affinity for Router service. If not set, None will be set as the default value |
"" |
router.service.sessionAffinityConfig |
Configuration for Router service Session Affinity. Used if the router.service.sessionAffinity is set |
{} |
router.service.externalTrafficPolicy |
Enable preservation of the client source IP. There are two available options: Cluster (default) and Local. Not supported for service type - ClusterIP |
"" |
router.resolver.dns |
Configures name server used to resolve names of upstream servers into addresses. If set to, it takes priority over the router.resolver.local |
"" |
router.resolver.local |
Allows you to use the DNS configuration of the container. If set to on, the standard path "/etc/resolv.conf" will be used. You can specify an arbitrary path |
on |
| Parameter | Description | Default |
|---|---|---|
doceditor.containerPorts.doceditor |
Doceditor container port | 5013 |
| Parameter | Description | Default |
|---|---|---|
login.containerPorts.login |
Login container port | 5011 |
| Parameter | Description | Default |
|---|---|---|
socket.containerPorts.socket |
Socket additional container port | 9899 |
| Parameter | Description | Default |
|---|---|---|
ssoauth.containerPorts.sso |
Ssoauth additional container port | 9834 |
| Parameter | Description | Default |
|---|---|---|
identity.enabled |
Enables Identity appications: identity.authorization, identity.api |
false |
identity.serviceAccount.create |
Enable Identity ServiceAccount creation. The Role and the RoleBinding required to build a cluster from identity replicas will be applied. If disabled, the common serviceAccount will be used |
true |
identity.env.springProfilesActive |
Defines the environment variable to override/pick Spring profile. Default is dev |
dev |
identity.env.multicast.enabled |
Defines whether multicast discovery will be used | false |
identity.env.kubernetes.enabled |
Defines whether k8s service discovery will be used | true |
| Parameter | Description | Default |
|---|---|---|
identity.authorization.containerPorts.authorization |
Identity additional container port | 8080 |
| Parameter | Description | Default |
|---|---|---|
identity.api.containerPorts.api |
Identity API additional container port | 9090 |
| Parameter | Description | Default |
|---|---|---|
proxyFrontend.enabled |
Enables Proxy Frontend installation | false |
proxyFrontend.initContainers |
Defines containers that run before Proxy Frontend container in the Proxy Frontend pod | [] |
proxyFrontend.image.repository |
Proxy Frontend container image repository | nginx |
proxyFrontend.image.tag |
Proxy Frontend container image tag | latest |
proxyFrontend.containerPorts.http |
Proxy Frontend HTTP container port | 80 |
proxyFrontend.containerPorts.https |
Proxy Frontend HTTPS container port | 443 |
proxyFrontend.extraConf.customConfd.configMap |
The name of the ConfigMap containing additional custom configuration files. These files will be map in the /etc/nginx/conf.d/ directory of the container |
"" |
proxyFrontend.extraConf.customConfd.fileName |
The names of the configuration files containing additional custom configuration files. Must be the same as the key names in proxyFrontend.extraConf.customConfd.configMap. May contain multiple values |
example.conf |
proxyFrontend.hostname |
The hostname (domainname) by which the ONLYOFFICE DocSpace will be available | "" |
proxyFrontend.tls.secretName |
The name of the TLS secret containing the certificate and its associated key | tls |
proxyFrontend.tls.mountPath |
The path where the certificate and key will be mounted | /etc/nginx/ssl |
proxyFrontend.tls.crtName |
Name of the key containing the certificate | cert.crt |
proxyFrontend.tls.keyName |
Name of the key containing the key | cert.key |
proxyFrontend.service.existing |
The name of an existing service for Proxy Frontend. If not set, a service named proxy-frontend will be created |
"" |
proxyFrontend.service.annotations |
Map of annotations to add to the Proxy Frontend service | {} |
proxyFrontend.service.type |
Proxy Frontend service type | LoadBalancer |
proxyFrontend.service.sessionAffinity |
Session Affinity for Proxy Frontend. service. If not set, None will be set as the default value |
"" |
proxyFrontend.service.sessionAffinityConfig |
Configuration for Proxy Frontend service Session Affinity. Used if the proxyFrontend.service.sessionAffinity is set |
{} |
proxyFrontend.service.externalTrafficPolicy |
Enable preservation of the client source IP. There are two available options: Cluster (default) and Local. Not supported for service type - ClusterIP |
"" |
| Parameter | Description | Default |
|---|---|---|
docs.enabled |
Enables Onlyoffice Docs subchart installation. Set to false if you plan to use the already installed Onlyoffice Docs or install DocSpace without it |
true |
docs.connections.dbType |
The Database type. By default, the same Database connection is used as for DocSpace | mysql |
docs.connections.dbHost |
The IP address or the name of the Database host | mysql |
docs.connections.dbUser |
Database user | onlyoffice_user |
docs.connections.dbPort |
Database server port number | 3306 |
docs.connections.dbName |
Name of the Database database the application will be connected with. The database must already exist | docspace |
docs.connections.dbExistingSecret |
Name of existing secret to use for Database password. Must contain the key specified in docs.connections.dbSecretKeyName |
mysql |
docs.connections.dbSecretKeyName |
The name of the key that contains the Database user password. If you set a password in docs.connections.dbPassword, a secret will be automatically created, the key name of which will be the value set here |
mysql-password |
docs.connections.dbPassword |
Database user password. If set to, it takes priority over the docs.connections.dbExistingSecret |
"" |
docs.connections.redisHost |
The IP address or the name of the Redis host. By default, the same Redis connection is used as for DocSpace, except for docs.connections.redisDBNum |
redis-master |
docs.connections.redisPort |
The Redis server port number | 6379 |
docs.connections.redisUser |
The Redis user name | default |
docs.connections.redisDBNum |
Number of the Redis logical database to be selected | 1 |
docs.connections.redisExistingSecret |
Name of existing secret to use for Redis password. Must contain the key specified in docs.connections.redisSecretKeyName |
redis |
docs.connections.redisSecretKeyName |
The name of the key that contains the Redis user password. If you set a password in docs.connections.redisPassword, a secret will be automatically created, the key name of which will be the value set here |
redis-password |
docs.connections.redisPassword |
The password set for the Redis account. If set to, it takes priority over the docs.connections.redisExistingSecret |
"" |
docs.connections.redisNoPass |
Defines whether to use a Redis auth without a password. If the connection to Redis server does not require a password, set the value to true |
false |
docs.connections.amqpType |
Defines the AMQP server type. By default, the same RabbitMQ connection is used as for DocSpace | rabbitmq |
docs.connections.amqpHost |
The IP address or the name of the AMQP server | rabbitmq |
docs.connections.amqpPort |
The port for the connection to AMQP server | 5672 |
docs.connections.amqpVhost |
The virtual host for the connection to AMQP server | / |
docs.connections.amqpUser |
The username for the AMQP server account | user |
docs.connections.amqpProto |
The protocol for the connection to AMQP server | amqp |
docs.connections.amqpExistingSecret |
The name of existing secret to use for AMQP server password. Must contain the key specified in docs.connections.amqpSecretKeyName |
rabbitmq |
docs.connections.amqpSecretKeyName |
The name of the key that contains the AMQP server user password. If you set a password in docs.connections.amqpPassword, a secret will be automatically created, the key name of which will be the value set here |
rabbitmq-password |
docs.connections.amqpPassword |
AMQP server user password. If set to, it takes priority over the docs.connections.amqpExistingSecret |
"" |
docs.service.port |
ONLYOFFICE Docs service port | 80 |
docs.license.existingClaim |
Name of the existing PVC in which the license is stored. Must contain the file license.lic. By default, a PVC is connected, in which a license is added when using DocSpace Enterprise |
docspace-data |
docs.jwt.existingSecret |
The name of an existing secret containing variables for jwt. By default, the jwt secret is used, which will be created with values from the jwt DocSpace | docspace-jwt |
docs.docservice.image.repository |
Docservice container image repository. Depending on your license type, add the suffix "-de" - Developer Edition or "-ee" Enterprise Edition. By default - Community version | onlyoffice/docs-docservice |
docs.proxy.image.repository |
Proxy container image repository. Depending on your license type, add the suffix "-de" - Developer Edition or "-ee" Enterprise Edition. By default - Community version | onlyoffice/docs-proxy |
docs.converter.image.repository |
Converter container image repository. Depending on your license type, add the suffix "-de" - Developer Edition or "-ee" Enterprise Edition. By default - Community version | onlyoffice/docs-converter |
docs.upgrade.job.enabled |
Enable the execution of job Docs pre-upgrade before upgrading. Set to false when upgrading to version 3.0.0 from earlier. When installing 3.0.0 and also when upgrading from version 3.0.0 to a later one, it should be set to true |
true |
docs.clearCache.job.enabled |
Enable the execution of job Docs Clear Cache after upgrading. Set to false when upgrading to version 3.0.0 from earlier. When installing 3.0.0 and also when upgrading from version 3.0.0 to a later one, it should be set to true |
true |
| Parameter | Description | Default |
|---|---|---|
ingress.enabled |
Enable the creation of an ingress for the ONLYOFFICE DocSpace | false |
ingress.annotations |
Map of annotations to add to the Ingress | kubernetes.io/ingress.class: nginx, nginx.ingress.kubernetes.io/proxy-body-size: 100m |
ingress.ingressClassName |
Used to reference the IngressClass that should be used to implement this Ingress | nginx |
ingress.tls.enabled |
Enable TLS for the ONLYOFFICE DocSpace | false |
ingress.tls.secretName |
Secret name for TLS to mount into the Ingress | tls |
ingress.host |
Ingress hostname for the ONLYOFFICE DocSpace | "" |
| Parameter | Description | Default |
|---|---|---|
install.job.enabled |
Enable the execution of job pre-install before installing ONLYOFFICE DocSpace | true |
install.job.annotations |
Defines annotations that will be additionally added to Install Job. If set to, it takes priority over the commonAnnotations |
{} |
install.job.podAnnotations |
Map of annotations to add to the Install Job Pod. If set to, it takes priority over the podAnnotations |
{} |
install.job.podSecurityContext.enabled |
Enable security context for the Install Job pod | false |
install.job.customPodAntiAffinity |
Prohibiting the scheduling of Install Job Pod relative to other Pods containing the specified labels on the same node | {} |
install.job.podAffinity |
Defines Pod affinity rules for Install Job Pod scheduling by nodes relative to other Pods | {} |
install.job.nodeAffinity |
Defines Node affinity rules for Install Job Pod scheduling by nodes | {} |
install.job.nodeSelector |
Node labels for Install Job pod assignment. If set to, it takes priority over the nodeSelector |
{} |
install.job.tolerations |
Tolerations for Install Job pod assignment. If set to, it takes priority over the tolerations |
[] |
install.job.containerSecurityContext.enabled |
Enable security context for containers in Install Job pod | false |
install.job.initContainers.migrationRunner.enabled |
Enable database initialization | true |
install.job.initContainers.migrationRunner.image.repository |
Job by pre-install Migration Runner container image repository | onlyoffice/docspace-migration-runner |
install.job.initContainers.migrationRunner.image.tag |
Job by pre-install Migration Runner container image tag. If set to, it takes priority over the images.tag |
"" |
install.job.initContainers.migrationRunner.image.pullPolicy |
Job by pre-install Migration Runner container image pull policy | IfNotPresent |
install.job.initContainers.migrationRunner.resources.requests |
The requested resources for the Job pre-install Migration Runner container | memory, cpu |
install.job.initContainers.migrationRunner.resources.limits |
The resources limits for the Job pre-install Migration Runner container | memory, cpu |
upgrade.job.enabled |
Enable the execution of job pre-upgrade before upgrading ONLYOFFICE DocSpace | true |
upgrade.job.annotations |
Defines annotations that will be additionally added to Upgrade Job. If set to, it takes priority over the commonAnnotations |
{} |
upgrade.job.podAnnotations |
Map of annotations to add to the Upgrade Job Pod. If set to, it takes priority over the podAnnotations |
{} |
upgrade.job.podSecurityContext.enabled |
Enable security context for the Upgrade Job pod | false |
upgrade.job.customPodAntiAffinity |
Prohibiting the scheduling of Upgrade Job Pod relative to other Pods containing the specified labels on the same node | {} |
upgrade.job.podAffinity |
Defines Pod affinity rules for Upgrade Job Pod scheduling by nodes relative to other Pods | {} |
upgrade.job.nodeAffinity |
Defines Node affinity rules for Upgrade Job Pod scheduling by nodes | {} |
upgrade.job.nodeSelector |
Node labels for Upgrade Job pod assignment. If set to, it takes priority over the nodeSelector |
{} |
upgrade.job.tolerations |
Tolerations for Upgrade Job pod assignment. If set to, it takes priority over the tolerations |
[] |
upgrade.job.containerSecurityContext.enabled |
Enable security context for containers in Upgrade Job pod | false |
upgrade.job.initContainers.migrationRunner.enabled |
Enable database update | true |
upgrade.job.initContainers.migrationRunner.image.repository |
Job by pre-upgrade Migration Runner container image repository | onlyoffice/docspace-migration-runner |
upgrade.job.initContainers.migrationRunner.image.tag |
Job by pre-upgrade Migration Runner container image tag. If set to, it takes priority over the images.tag |
"" |
upgrade.job.initContainers.migrationRunner.image.pullPolicy |
Job by pre-upgrade Migration Runner container image pull policy | IfNotPresent |
upgrade.job.initContainers.migrationRunner.resources.requests |
The requested resources for the Job pre-upgrade Migration Runner container | memory, cpu |
upgrade.job.initContainers.migrationRunner.resources.limits |
The resources limits for the Job pre-upgrade Migration Runner container | memory, cpu |
upgrade.job.initContainers.rootless.enabled |
Enable the rootless initContainer to change file ownership | true |
upgrade.job.initContainers.rootless.image.repository |
rootless initContainer image repository | onlyoffice/docs-utils |
upgrade.job.initContainers.rootless.image.tag |
rootless initContainer image tag. If set to, it takes priority over the images.tag |
8.2.2-1 |
upgrade.job.initContainers.rootless.image.pullPolicy |
rootless initContainer image pull policy | IfNotPresent |
upgrade.job.initContainers.rootless.resources.requests.memory |
The requested Memory for the rootless initContainer | 256Mi |
upgrade.job.initContainers.rootless.resources.requests.cpu |
The requested CPU for the rootless initContainer | 100m |
upgrade.job.initContainers.rootless.resources.limits.memory |
The Memory limits for the rootless initContainer | 1Gi |
upgrade.job.initContainers.rootless.containerSecurityContext.enabled |
Enable security context for the rootless initContainer | true |
upgrade.job.initContainers.rootless.containerSecurityContext.runAsUser |
User ID for the DocSpace rootless initContainer. When performing a clean install of 3.0+ images or upgrading from version 3.0+ to a later version, you can specify uid=104 | 0 |
upgrade.job.initContainers.rootless.containerSecurityContext.runAsGroup |
Group ID for the DocSpace rootless initContainer. When performing a clean install of 3.0+ images or upgrading from version 3.0+ to a later version, you can specify gid=107 | 0 |
upgrade.job.initContainers.rootless.containerSecurityContext.allowPrivilegeEscalation |
Controls whether a process can gain more privileges than its parent process | false |
upgrade.job.initContainers.rootless.containerSecurityContext.seLinuxOptions |
Defines SELinux labels for the DocSpace rootless initContainer | {} |
upgrade.job.initContainers.rootless.containerSecurityContext.seccompProfile |
Defines the Seccomp profile for the DocSpace rootless initContainer | type: RuntimeDefault |
upgrade.job.initContainers.rootless.containerSecurityContext.capabilities |
Defines the privileges granted to the process | drop: ["ALL"] |
upgrade.job.docsInitDB.enabled |
Enable the Init DB for Docs container to create tables required for Docs to work. Set to true when upgrading to version 3.0.0 from earlier. When installing 3.0.0 and also when upgrading from version 3.0.0 to a later one, it should be set to false |
false |
elasticsearchClearIndexes.job.enabled |
Enable the execution of job elasticsearchClearIndexes before upgrading DocSpace. If you are using Opensearch or an external Elasticsearch, you can set it to false |
true |
elasticsearchClearIndexes.job.annotations |
Defines annotations that will be additionally added to elasticsearchClearIndexes Job. If set to, it takes priority over the commonAnnotations |
{} |
elasticsearchClearIndexes.job.podAnnotations |
Map of annotations to add to the elasticsearchClearIndexes Job Pod. If set to, it takes priority over the podAnnotations |
{} |
elasticsearchClearIndexes.job.podSecurityContext.enabled |
Enable security context for the elasticsearchClearIndexes Job pod | false |
elasticsearchClearIndexes.job.customPodAntiAffinity |
Prohibiting the scheduling of elasticsearchClearIndexes Job Pod relative to other Pods containing the specified labels on the same node | {} |
elasticsearchClearIndexes.job.podAffinity |
Defines Pod affinity rules for elasticsearchClearIndexes Job Pod scheduling by nodes relative to other Pods | {} |
elasticsearchClearIndexes.job.nodeAffinity |
Defines Node affinity rules for elasticsearchClearIndexes Job Pod scheduling by nodes | {} |
elasticsearchClearIndexes.job.nodeSelector |
Node labels for elasticsearchClearIndexes Job pod assignment. If set to, it takes priority over the nodeSelector |
{} |
elasticsearchClearIndexes.job.tolerations |
Tolerations for elasticsearchClearIndexes Job pod assignment. If set to, it takes priority over the tolerations |
[] |
elasticsearchClearIndexes.job.containerSecurityContext.enabled |
Enable security context for containers in elasticsearchClearIndexes Job pod | false |
elasticsearchClearIndexes.job.resources.requests |
The requested resources for the Job elasticsearchClearIndexes container | memory, cpu |
elasticsearchClearIndexes.job.resources.limits |
The resources limits for the Job elasticsearchClearIndexes container | memory, cpu |
| Parameter | Description | Default |
|---|---|---|
opensearch.enabled |
Enables Opensearch installation | true |
opensearch.initContainers.securityContext.enabled |
Enable security context for Opensearch change-volume-owner initContainer container in pod | false |
opensearch.initContainers.resources.requests |
The requested resources for the Opensearch change-volume-owner initContainer | memory, cpu |
opensearch.initContainers.resources.limits |
The resources limits for the Opensearch change-volume-owner initContainer | memory, cpu |
opensearch.initContainers.custom |
Custom Opensearch initContainers parameters. Additional containers that run before Elasticsearch container in a Pod | [] |
opensearch.image.repository |
Opensearch container image repository | onlyoffice/opensearch |
opensearch.image.tag |
Opensearch container image tag | 7.16.3 |
opensearch.persistence.annotations |
Defines annotations that will be additionally added to Opensearch PVC. If set to, it takes priority over the commonAnnotations |
{} |
opensearch.persistence.storageClass |
PVC Storage Class for Opensearch volume | "nfs" |
opensearch.persistence.accessModes |
Opensearch Persistent Volume access modes | ReadWriteOnce |
opensearch.persistence.size |
PVC Storage Request for Opensearch volume | 30Gi |
opensearch.env.discoveryType |
Determines the cluster discovery type. Set to "single-node" for a single-node cluster | `single-node |
opensearch.env.disableSecurityPlugin |
disables the security plugin | true |
opensearch.env.disableInstallDemoConfig |
disables the installation of demo configuration | true |
opensearch.env.bootstrapMemoryLock |
determines whether JVM should lock memory | true |
opensearch.env.ESJAVAOPTS |
defines JVM options | -Xms2g -Xmx2g -Dlog4j2.formatMsgNoLookups=true |
opensearch.env.indicesFieldDataCacheSize |
sets the size of the index field data cache | 30% |
opensearch.env.indicesMemoryIndexBufferSize |
sets the size of the in-memory index buffer | 30% |
| Parameter | Description | Default |
|---|---|---|
tests.enabled |
Enable the resources creation necessary for ONLYOFFICE DocSpace launch testing and connected dependencies availability testing. These resources will be used when running the helm test command |
true |
tests.annotations |
Defines annotations that will be additionally added to Test Pod. If set to, it takes priority over the commonAnnotations |
{} |
tests.podSecurityContext.enabled |
Enable security context for the Test pod | false |
tests.customPodAntiAffinity |
Prohibiting the scheduling of Test Pod relative to other Pods containing the specified labels on the same node | {} |
tests.podAffinity |
Defines Pod affinity rules for Test Pod scheduling by nodes relative to other Pods | {} |
tests.nodeAffinity |
Defines Node affinity rules for Test Pod scheduling by nodes | {} |
tests.nodeSelector |
Node labels for Test pod assignment. If set to, it takes priority over the nodeSelector |
{} |
tests.tolerations |
Tolerations for Test pod assignment. If set to, it takes priority over the tolerations |
[] |
tests.image.repository |
Test container image name | onlyoffice/docs-utils |
tests.image.tag |
Test container image tag | 8.2.2-1 |
tests.image.pullPolicy |
Test container image pull policy | IfNotPresent |
tests.containerSecurityContext.enabled |
Enable security context for the Test container | false |
tests.resources.requests |
The requested resources for the Test container | memory: "256Mi", cpu: "200m" |
tests.resources.limits |
The resources limits for the Test container | memory: "1Gi", cpu: "1000m" |
You should skip step[#1.1] if you are going to expose ONLYOFFICE DocSpace via HTTPS
This type of exposure has the least overheads of performance, it creates a loadbalancer to get access to ONLYOFFICE DocSpace. Use this type of exposure if you use external TLS termination, and don't have another WEB application in the k8s cluster.
To expose ONLYOFFICE DocSpace via service, set the router.service.type parameter to LoadBalancer:
$ helm install [RELEASE_NAME] onlyoffice/docspace --set router.service.type=LoadBalancer,router.service.port.external=8092
Run the following command to get the router service IP:
$ kubectl get service router -o jsonpath="{.status.loadBalancer.ingress[*].ip}"After that, ONLYOFFICE DocSpace will be available at http://DOCSPACE-SERVICE-IP/.
If the service IP is empty, try getting the router service hostname:
$ kubectl get service router -o jsonpath="{.status.loadBalancer.ingress[*].hostname}"In this case, ONLYOFFICE DocSpace will be available at http://DOCSPACE-SERVICE-HOSTNAME/.
To install the Nginx Ingress Controller to your cluster, run the following command:
$ helm install nginx-ingress ingress-nginx/ingress-nginx --set controller.publishService.enabled=true,controller.replicaCount=2See more detail about installing Nginx Ingress Controller via Helm here.
You should skip step[2.1.2] if you are going to expose ONLYOFFICE DocSpace via HTTPS
This type of exposure has more overheads of performance compared with exposure via service, it also creates a loadbalancer to get access to ONLYOFFICE DocSpace. Use this type if you use external TLS termination and when you have several WEB applications in the k8s cluster. You can use the one set of ingress instances and the one loadbalancer for those. It can optimize the entry point performance and reduce your cluster payments, cause providers can charge a fee for each loadbalancer.
To expose ONLYOFFICE DocSpace via ingress HTTP, set the ingress.enabled parameter to true:
$ helm install [RELEASE_NAME] onlyoffice/docspace --set ingress.enabled=true
Run the following command to get the docspace ingress IP:
$ kubectl get ingress docspace -o jsonpath="{.status.loadBalancer.ingress[*].ip}"After that, ONLYOFFICE DocSpace will be available at http://DOCSPACE-INGRESS-IP/.
If the ingress IP is empty, try getting the docspace ingress hostname:
$ kubectl get ingress docspace -o jsonpath="{.status.loadBalancer.ingress[*].hostname}"In this case, ONLYOFFICE DocSpace will be available at http://DOCSPACE-INGRESS-HOSTNAME/.
This type of exposure allows you to enable internal TLS termination for ONLYOFFICE DocSpace.
Create the tls secret with an ssl certificate inside.
Put the ssl certificate and the private key into the tls.crt and tls.key files and then run:
$ kubectl create secret generic tls \
--from-file=./tls.crt \
--from-file=./tls.key$ helm install [RELEASE_NAME] onlyoffice/docspace --set ingress.enabled=true,ingress.tls.enabled=true,ingress.tls.secretName=tls,ingress.host=example.com
Run the following command to get the docspace ingress IP:
$ kubectl get ingress docspace -o jsonpath="{.status.loadBalancer.ingress[*].ip}"If the ingress IP is empty, try getting the docspace ingress hostname:
$ kubectl get ingress docspace -o jsonpath="{.status.loadBalancer.ingress[*].hostname}"Associate the docspace ingress IP or hostname with your domain name through your DNS provider.
After that, ONLYOFFICE DocSpace will be available at https://your-domain-name/.
In ONLYOFFICE DocSpace appVersion 2.5.0, ElasticSearch is being replaced with OpenSearch, which will require reindexing, taking some time.
For proper reindexing before updating ONLYOFFICE DocSpace to version 2.5.0, execute the following command:
-
If
file-servicesis deployed as a StatefulSet:kubectl scale statefulset files-services --replicas=0
-
Otherwise, if deployed as a Deployment:
kubectl scale deployment files-services --replicas=0
Then proceed with the ONLYOFFICE DocSpace update.
NOTE: If you have an external Elasticsearch installed, please follow these steps before updating:
- Reduce the replica count of
files-servicesto 0, as described above. - In the configmap and job files named
elasticsearch-clear-indexes.yaml, replace the values inspec.template.spec.containers.env[(name=="MYSQL_PASSWORD")].valueand, if necessary, inspec.template.spec.containers.env[(name=="MYSQL_USER")].valuewith your own values. - Apply these files
elasticsearch-clear-indexes.yaml:
kubectl apply -f https://raw.githubusercontent.com/ONLYOFFICE/Kubernetes-DocSpace/main/sources/elasticsearch-clear-indexes.yamlAfter successfully executing the Pod elasticsearch-clear-indexes that created the Job, delete this Job with the following command:
kubectl delete -f https://raw.githubusercontent.com/ONLYOFFICE/Kubernetes-DocSpace/main/sources/elasticsearch-clear-indexes.yamlYou can test ONLYOFFICE DocSpace services availability and access to connected dependencies by running the following command:
$ helm test [RELEASE_NAME] -n <NAMESPACE>The output should have the following line:
Phase: SucceededTo view the log of the Pod running as a result of the helm test command, run the following command:
$ kubectl logs -f test-docspace -n <NAMESPACE>The ONLYOFFICE DocSpace services availability check is considered a priority, so if it fails with an error, the test is considered to be failed.
After this, you can delete the test-docspace Pod by running the following command:
$ kubectl delete pod test-docspace -n <NAMESPACE>Note: This testing is for informational purposes only and cannot guarantee 100% availability results. It may be that even though all checks are completed successfully, an error occurs in the application. In this case, more detailed information can be found in the application logs.