Skip to content

Commit e3a485e

Browse files
committed
Update verbiage on k8s page
1 parent bf05b85 commit e3a485e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

kubernetes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ There are a few caveats to be aware of when using the NetApp Data Science Toolki
1414

1515
### Creating and Cloning Data Volumes in a Kubernetes Environment
1616

17-
Data volumes that are created using the NetApp Data Science Toolkit will not automatically be represented by PVCs (PersistentVolumeClaims) in the Kubernetes cluster. In order to create a PVC for a volume that was created using the NetApp Data Science Toolkit, you will need to import the volume using Trident's volume import functionality. To avoid this extra step, NetApp recommends using Trident's native volume provisioning and volume cloning capabilities in place of the Netapp Data Science Toolkit's "create volume" and "clone volume" functions when operating in a Kubernetes environment. Refer to the [Trident documentation](https://netapp-trident.readthedocs.io/) for more details and examples.
17+
NetApp recommends using Trident's native volume provisioning and volume cloning capabilities in place of the Netapp Data Science Toolkit's "create volume" and "clone volume" functions when operating in a Kubernetes environment. Trident automates the process of volume provisioning in Kubernetes. If you have Trident installed in your Kubernetes cluster, then all that you have to do to provision a new volume is create a PVC (PersistentVolumeClaim). When you create a PVC, Trident will automatically provision a data volume and bind it to the PVC. Refer to the [Trident documentation](https://netapp-trident.readthedocs.io/) for more details and examples.
1818

1919
### Mount Operation within Container
2020

21-
It is not possible to mount a volume using the NetApp Data Science Toolkit while operating within a container. Mount operations are generally not permitted wtihin containers. Kubernetes handles the mounting of volume(s) at the time that a container is provisioned. Any volume mounts that are needed for a specific Kubernetes pod must be specified within the pod definition. Refer to the [Trident documentation](https://netapp-trident.readthedocs.io/) for more details and examples.
21+
It is not possible to mount a volume using the NetApp Data Science Toolkit while operating within a container. Mount operations are generally not permitted wtihin containers. Kubernetes handles the mounting of volume(s) at the time that a container is provisioned. Any volume mounts that are needed for a specific Kubernetes pod must be specified within the pod definition. If you are using Trident, refer to the [Trident documentation](https://netapp-trident.readthedocs.io/) for more details and examples.
2222

2323
### Trident Volume Names
2424

0 commit comments

Comments
 (0)