Working with TFS

Access the Console

1. Log into the Thalassa Cloud Console
2. Navigate to IaaS → Storage → TFS
3. Click Create TFS Instance

Configure TFS Instance

Configure your TFS instance:

• Name: Choose a descriptive name (e.g., production-tfs)
• VPC: Select the VPC where the TFS instance will be deployed
• Subnet: Select a subnet within the VPC
• Description: Optional description of the TFS instance purpose

Configure Security Groups (Optional)

Attach a security group that allows NFS traffic:

• Protocol: TCP
• Port: 2049 (NFS)
• Source: Subnet CIDR or specific IP ranges that need access

Ensure the security group allows inbound NFS traffic from:

• Your VPC subnets (for VM access)
• Kubernetes node subnets (for Kubernetes integration)
• Using CIDR, IP another Security Group

Create NFS Exports

After the TFS instance is created, create NFS exports:

1. Navigate to your TFS instance
2. Click Create Export
3. Configure the export:
   • Export Path: Path for the export (e.g., /app-data, /shared-files)
   • Description: Optional description

You can create multiple exports from a single TFS instance to organise data by application, team, or purpose.

Check TFS Status

In the console, monitor the TFS instance status. The instance will show:

• Status: Creating → Ready
• Endpoint: Available when ready
• Port: Typically 2049 for NFS

Wait until the status changes to Ready before attempting to mount.

Verify Endpoint Information

Once ready, note the following information:

• TFS Endpoint: IP address or hostname (e.g., 10.0.1.100 or tfs-12345678.internal)
• Port: NFS port (typically 2049)
• Export Path: The path you configured (e.g., /app-data)

Install NFS Client

SSH into your virtual machine and install the NFS client:

Ubuntu/Debian:

sudo apt update
sudo apt install -y nfs-common

CentOS/RHEL/Fedora:

sudo yum install -y nfs-utils
# or for newer versions
sudo dnf install -y nfs-utils

Create Mount Point

Create a directory where the TFS export will be mounted:

sudo mkdir -p /mnt/tfs

Use a descriptive path that indicates the export’s purpose (e.g., /mnt/app-data, /mnt/shared-files).

Mount the TFS Export

Mount the TFS export using NFSv4.1:

sudo mount -t nfs4 -o vers=4.1 <tfs-endpoint>:/<export-path> /mnt/tfs

Replace:

• <tfs-endpoint> with your TFS endpoint IP or hostname
• <export-path> with your export path (e.g., /app-data)

Example:

sudo mount -t nfs4 -o vers=4.1 10.0.1.100:/app-data /mnt/tfs

Verify Mount

Verify the mount is successful:

df -h | grep /mnt/tfs
mount | grep /mnt/tfs

Test write access:

sudo touch /mnt/tfs/test-file
sudo rm /mnt/tfs/test-file

Configure Persistent Mount

To mount TFS automatically after VM reboots, add it to /etc/fstab:

sudo nano /etc/fstab

Add the following line:

<tfs-endpoint>:/<export-path> /mnt/tfs nfs4 vers=4.1,defaults,_netdev 0 0

Example:

10.0.1.100:/app-data /mnt/tfs nfs4 vers=4.1,defaults,_netdev 0 0

Mount options explained:

• vers=4.1: Use NFSv4.1 protocol
• defaults: Use default mount options
• _netdev: Wait for network to be available before mounting

Test the fstab configuration:

sudo mount -a

If there are no errors, the configuration is correct.

Install NFS CSI Driver

Install the NFS CSI driver using Helm:

helm repo add csi-driver-nfs https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/charts
helm repo update
helm install csi-driver-nfs csi-driver-nfs/csi-driver-nfs \
  --namespace kube-system \
  --version v4.1.0

Verify the installation:

kubectl get pods -n kube-system | grep csi-nfs

Create StorageClass

Create a StorageClass for TFS:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: tfs-nfs
provisioner: nfs.csi.k8s.io
parameters:
  server: <tfs-endpoint>
  share: /<export-path>
allowVolumeExpansion: true
volumeBindingMode: Immediate
mountOptions:
  - nfsvers=4.1,_netdev,hard,noatime,timeo=20,retrans=3

Replace:

• <tfs-endpoint> with your TFS endpoint IP or hostname
• <export-path> with your export path

Example:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: tfs-nfs
provisioner: nfs.csi.k8s.io
parameters:
  server: 10.0.1.100
  share: /app-data
allowVolumeExpansion: true
volumeBindingMode: Immediate
mountOptions:
  - nfsvers=4.1,_netdev,hard,noatime,timeo=20,retrans=3

Apply the StorageClass:

kubectl apply -f tfs-storageclass.yaml

Create PersistentVolumeClaim

Create a PersistentVolumeClaim using the StorageClass:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: tfs-pvc
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: tfs-nfs
  resources:
    requests:
      storage: 100Gi

Apply the PersistentVolumeClaim:

kubectl apply -f tfs-pvc.yaml

The NFS CSI driver will automatically create a PersistentVolume and mount it when attached to a Pod.