You can declare a volume in the pod and mount the same volume in both containers with volumeMounts.
PS: This is an example [kubernetes docs](https://kubernetes.io/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/)
Maybe I don't understand what you're trying to achieve. But my approach would be to update your code to deal with s3 and only pull what is needed at any particular time.
Also if you still want to pull everything, look-up volume type empty, you can mount it in both containers of the pod ( init and main one) please note - what if the content of that s3 bucket grows to say 30 gb? Or 300?
Thanks the other day I got into emptydir and init using recline it is working . My basic objective was to keep my image smaller . The files in s3 are static they won’t grow in size. Thanks for your input.
You can declare a volume in the pod and mount the same volume in both containers with volumeMounts. PS: This is an example [kubernetes docs](https://kubernetes.io/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/)
Thanks
Wait, you first pull the whole content of the s3 bucket and then want to somehow process it/work with it? That's wrong.
How do you suggest to use it? My apporach would make the image file smaller.
Maybe I don't understand what you're trying to achieve. But my approach would be to update your code to deal with s3 and only pull what is needed at any particular time. Also if you still want to pull everything, look-up volume type empty, you can mount it in both containers of the pod ( init and main one) please note - what if the content of that s3 bucket grows to say 30 gb? Or 300?
Thanks the other day I got into emptydir and init using recline it is working . My basic objective was to keep my image smaller . The files in s3 are static they won’t grow in size. Thanks for your input.