How to install Thinkfree Office on Kubernetes

Modified on Tue, 15 Jul at 12:57 PM

This document explains how to install Thinkfree Office in a Kubernetes environment.

It is based on standard customer environments and assumes that the following prerequisites are met:

  • AWS CLI and Helm must be installed

  • AWS authentication must be completed using credentials provided by your Thinkfree representative

  • Kubernetes integration must be completed prior to deployment

If these requirements are not yet fulfilled, please refer to the pre-installation preparation guide.



Install Thinkfree Office

1) Setting variable values

ACCOUNT=958750823146
REGION=ap-northeast-2
SECRET_NAME=thinkfree-office-ecr-secret
EMAIL=contact@thinkfree.com
TOKEN=`aws ecr get-login-password --region=${REGION}`
  • SECRET_NAME: You can change it to another name.


2) Create Secret

In order to properly execute the command below, an environment capable of Kubernetes deployment must be configured.

kubectl create secret docker-registry ${SECRET_NAME} \
    --docker-server=https://${ACCOUNT}.dkr.ecr.${REGION}.amazonaws.com \
    --docker-username=AWS \
    --docker-password="${TOKEN}" \
    --docker-email="${EMAIL}"



3) Installation

1. AWS Certification

helm registry login --username AWS --password-stdin ${ACCOUNT}.dkr.ecr.${REGION}.amazonaws.com <<< "${TOKEN}"



2. Install Thinkfree Office

helm upgrade --install thinkfree oci://${ACCOUNT}.dkr.ecr.${REGION}.amazonaws.com/thinkfree-office-chart \
  --set image.pullSecrets[0]=${SECRET_NAME}
  • thinkfree: This is the part corresponding to the Release Name of the Helm Chart. You can change it to a different name.

    Also you can install a specific version (e.g. v2.5.5.1) of Thinkfree Office with the below example command :

helm upgrade --install thinkfree oci://${ACCOUNT}.dkr.ecr.${REGION}. amazonaws.com/thinkfree-office-chart \
 --set image.pullSecrets[0]=${SECRET_NAME}
 --version 2.5.5.1


ThinkfreeOffice Test


Once the installation is complete, you will see the following message:

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⡿⣟⣿⣻⣿⣻⣟⣿⣟⣿⣻⣿⣳⣦⣄⠀⠀⠀⠀⠀⠀⢠⡰⣜⢮⡫⣏⢯⡫⣏⢯⡫⣏⢯⡫⡯⠀⠀
⠀⠀⣿⣻⣽⣟⣾⣯⢿⣳⣿⣽⢷⣿⣽⢷⣟⣧⡄⠀⠀⢀⢼⢕⣝⢮⡳⡝⣎⢗⣝⢎⣗⢝⣎⢗⣝⢮⠀⠀
⠀⠀⣯⣿⢾⣯⡷⣿⣻⡿⣞⣯⡿⣷⣟⣿⣽⡷⣷⠀⠀⡮⣳⢳⢕⡗⡵⣝⢮⡳⣕⢗⣕⢗⣕⢗⣕⢗⠀⠀
⠀⠀⠈⠈⠁⠁⠉⠈⠈⠈⠁⠁⠉⢿⣾⣻⣾⣻⡿⡅⠨⣺⡪⣳⢳⡹⡕⠁⠁⠈⠈⠈⠀⠁⠈⠈⠀⠁⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣾⣻⡾⣯⣿⡂⠨⡺⣜⢮⡳⣝⢎⠀⠀⠀⡠⣔⢦⡢⡄⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣯⣷⢿⣻⣾⡂⠨⡫⡮⣳⡹⣜⢕⠀⠀⡪⣏⢮⡳⡝⡮⡢⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⡷⣟⣿⣯⣷⠅⠨⡳⣝⢮⡺⡪⡇⠀⠀⡫⡮⡳⣝⢮⡫⡎⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣟⣯⣷⢿⣾⠅⠨⡳⣕⢗⣝⡝⡎⠀⠀⠈⠪⠫⡺⠪⠊⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣯⡿⣾⢿⣽⠅⠨⣝⢮⢳⢕⢽⡱⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⡷⣿⣻⣿⣽⠅⠨⣺⢪⣫⢳⡳⡕⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣟⣯⣿⢾⣯⡃⠨⢮⡳⣕⢗⣕⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⣯⡿⣾⢿⣽⡂⠨⡳⣝⢼⢕⢧⢇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠽⡷⢿⢻⠿⡽⡂⠨⡳⠵⢝⠮⡳⠣⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
Thank you for installing ThinkfreeOffice.
Please follow the next steps.
1. Get ThinkfreeOffice administrator URL by running these commands:
  export POD_NAME=$(kubectl get pods -l "app=was" -o jsonpath="{.items[0].metadata.name}")
  kubectl port-forward $POD_NAME 8080:80
2. Open the browser and access ThinkfreeOffice administrator page through the following URL:
  (The container initialization process may take some time.)
  http://127.0.0.1:8080/cloud-office
3. Register the license key received on the administrator page.
4. You can access ThinkfreeOffice through the following URL:
  * Word Processor
  http://127.0.0.1:8080/cloud-office/api/local/sample.docx/open?app=WRITE_EDITOR&user_id=username&docId=tfoword
  * Spreadsheet
  http://127.0.0.1:8080/cloud-office/api/local/sample.xlsx/open?app=CALC_EDITOR&user_id=username&docId=tfocell
  * Presentation
  http://127.0.0.1:8080/cloud-office/api/local/sample.pptx/open?app=SHOW_EDITOR&user_id=username&docId=tfoshow
  * PDF
  http://127.0.0.1:8080/cloud-office/api/local/sample.pdf/open?app=PDF_VIEWER&user_id=username&docId=tfopdf



Next, set up Helm Chart for Thinkfree Office by following the guide here.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article