Volumes provide a way to connect UAIs to external data, whether they be Kubernetes managed objects, external file systems or files, host node files and directories, or remote networked data to be used within the UAI.
The following are examples of how volumes are commonly used by UAIs:
/etc/localtime maintained by the host nodeAny kind of volume recognized by the Kubernetes installation can be installed as a volume within UAS. In the case of Legacy Mode UAI creation without a default UAI Class, all configured volumes are used when creating UAIs. This can be controlled more precisely by defining and using UAI Classes. There is more information on Kubernetes volumes in the Kubernetes Documentation.
NOTE As with UAI images, registering a volume with UAS creates the configuration that will be used to create a UAI. If the underlying object referred to by the volume does not exist at the time the UAI is created,
the UAI will, in most cases, wait until the object becomes available before starting up. This will be visible in the UAI state which will eventually move to waiting.