Decouple ink and sideqik
Currently ink and sideqik need to share a volume. While I'm not sure what the thinking was behind how ink would scale up for multiple workers it seems like a shared volume might inhibit this. The classic pattern would be to use something like s3 for file storage and share references to files stored on s3.
Until this is fixed ink and sideqik will need to be run in the same pod or use AWS EFS. This is not natively supported by kubernetes but an addon is here.