This document outlines the steps required to prepare the environment for installing Thinkfree Office on Kubernetes.

Overview

• Set up the environment for installation

• Install the main application

• Perform AWS authentication using credentials provided by Thinkfree representative

Installing the main application

Install the program to obtain AWS certification. The guide document was written based on the Linux environment.

Installing AWS CLI

Firstly, you need to install the AWS CLI if it has not been already.

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip && rm -f awscliv2.zip
sudo ./aws/install && rm -rf ./aws

Installing Helm

Then you need to install Helm by issuing the below command.

curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash

You can verify if it was installed properly using the following command.

helm version --short
v3.16.1+g5a5449d

Install kubectl

curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.2/2024-07-12/bin/linux/amd64/kubectl
chmod +x ./kubectl && sudo mv ./kubectl /usr/local/bin

You can check if it was installed properly using the following command.

kubectl version --client
Client Version: v1.30.2-eks-1552ad0 
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3

AWS Certification

AWS authentication is required to download the container image and is based on credentials provided by Thinkfree. To obtain these credentials, please contact us at dev@thinkfree.com.

AWS Configuration

aws configure
AWS Access Key ID [None]: <Access Key received from Thinkfree>
AWS Secret Access Key [None]: <Secret Key received from Thinkfree> 
Default region name [None]: <AWS Region received from Thinkfree> 
Default output format [None]: <Default output format provided by Thinkfree>

You can check whether communication is normal by checking the IAM user ID as follows.

aws sts get-caller-identity
{ 
    "UserId": <Normal if value exists>, 
    "Account": <Normal if value exists>, 
    "Arn": <Normal if value exists> 
}

Kubernetes Integration

Update kubeconfig (on Amazon EKS )

You must link IAM credentials to appropriate Kubernetes permissions. To enable this, the infrastructure administrator should be granted sufficient privileges in advance. (Note: This document is based on Amazon EKS. If you are using a different platform, you’ll need to follow that platform’s standard method for integrating with Kubernetes.)

aws eks update-kubeconfig --region <REGION_CODE> --name <CLUSTER_NAME>

• REGION_CODE: Change to the region where the cluster is set up. You can find out by contacting your infrastructure manager.
• CLUSTER_NAME: Set the cluster name. You can find out by asking your infrastructure manager.

Check normal operation

You can check if it is working properly with the following command.

kubectl get svc
NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE 
service/kubernetes   ClusterIP   172.20.0.1   <none>        443/TCP   1m