Testing NFS Access and Setting Ownership to Kinetic UUID
Process
Once your NFS has been set up, you must test access and set ownership to use the Kinetic Data Universally Unique Identifier (UUID).
NFS Server and IP Method
Follow these steps to perform the test and set ownership if you are using an NFS Server and IP address:
- Run the following command to start a busybox instance:
$ kubectl run -it --privileged --image busybox -- busybox-sh $ kubectl run \ -it \ --privileged \ --image busybox \ --env="NFS_SERVER_IP=<NFS_SERVER_IP>" \ --env="NFS_SERVER_PORT=<NFS_SERVER_PORT>" \ -- busybox-sh
- From the busybox shell, run the following command:
mkdir -p /mnt/nfs mount -t nfs4 $NFS_SERVER_IP:$NFS_SERVER_PORT:/ /mnt/nfs
- Run the following command to set ownership to the Kinetic Data UUID:
# chown -R 55101:55101 /mnt/nfs # chmod g+s /mnt/nfs
- Run the following command to stop the busybox instance:
$ kubectl delete pod busybox-sh
NFS Service with Access Point URL Method:
Follow these steps to perform the test and set ownership if you are using an NFS Service with an Access Point URL:
- Run the following command to start a busybox instance:
$ kubectl run -it --privileged --image busybox -- busybox-sh $ kubectl run \ -it \ --privileged \ --image busybox \ --env"ACCESS_POINT_URL=<ACCESS_POINT_URL>" \ -- busybox-sh
- From the busybox shell, run the following command:
# mkdir -p /mnt/nfs && mount -t nfs4 $ACCESS_POINT_URL:/ /mnt/nfs
- Run the following command to set ownership to the Kinetic Data UUID:
# chown -R 55101:55101 /mnt/nfs # chmod g+s /mnt/nfs
- Run the following command to stop the busybox instance:
$ kubectl delete pod busybox-sh
Updated 3 months ago