Tackle needs RWX volumes for multi-node cluster installations. If the default storage class does not support RWX, the user must define the rwx_storage_class property in the Tackle resource specification. As with any RWX storage, the permissions need to support read/write by multiple (linux users).  For example: NFS must be rwxrwxrwx or enable root_squash.

When rwx_storage_class not defined and the default storage class does not support RWX, task pods will get stuck in PENDING with events indicating that the volume is busy.

When rwx_storage_class has insufficient permission to properly support RWX, tasks will fail with Permission Denied when attempting to write to the volume.

While we're at it, all of these settings need to be included in MTA documentation.