K8S has a very different system of volumes which is separate from Docker. Docs are here: https://kubernetes.io/docs/concepts/storage/volumes/
For K8S you mainly need to consider what your running K8S on, AWS, GCP, bare metal etc? As well as what you are storing on your volumes and if they only need to stick around for the lifetime of the pod, or need to be kept for longer. In most cases when we are talking about file storage over the course of an apps lifetime (i.e. needs to persist even when deploying a new pod/version) the general direction is to store files in blob storage such as AWS S3. With Django this is pretty easy to do with django-storages ( https://django-storages.readthedocs.io/en/latest/). In some cases this isn't possible, for instance storing large ML models between multiple pods - in which case you will likely need to create persistentVolumeClaim using something like AWS EFS which involves a bit more manual work. In a few cases it may be that the data should be shipped to a database... The right path varies wildly depending on what you think you need volumes for. On Monday, October 14, 2019 at 10:43:45 AM UTC+1, vineet daniel wrote: > > in reference to kubernetes cluster as well? with multiple containers? > developer pushes the code to git and that invokes kube pipeline where does > volume come into picture here. I might be wrong here and that's why need > clarity on this. May be we are thinking differently. > > Regards > Vineet Daniel > Cell : +918527565696 > Websites : Blog <http://vineetdaniel.blogspot.com> | Linkedin > <http://in.linkedin.com/in/vineetdaniel> | Twitter > <https://twitter.com/vineetdaniel> > > > > > On Mon, Oct 14, 2019 at 2:40 PM Nick Sarbicki <nick.a...@gmail.com > <javascript:>> wrote: > >> You would use volumes in the same way regardless of how git is used and >> your CI/CD is setup. >> >> Documentation on volumes in docker is here: >> https://docs.docker.com/storage/volumes/ and for compose here: >> https://docs.docker.com/compose/compose-file/#volume-configuration-reference >> >> On Monday, October 14, 2019 at 8:15:46 AM UTC+1, vineet daniel wrote: >>> >>> How would one use volumes if containers are to initiated after git >>> merge/push ? (CI/CD setup). >>> >>> Regards >>> Vineet Daniel >>> Cell : +918527565696 >>> Websites : Blog <http://vineetdaniel.blogspot.com> | Linkedin >>> <http://in.linkedin.com/in/vineetdaniel> | Twitter >>> <https://twitter.com/vineetdaniel> >>> >>> >>> >>> >>> On Thu, Oct 10, 2019 at 10:13 PM Nick Sarbicki <nick.a...@gmail.com> >>> wrote: >>> >>>> Don't use git inside the container, this is not the standard way of >>>> doing things. >>>> >>>> Docker has its own guide for using django with compose. This works fine >>>> for a single server setup: https://docs.docker.com/compose/django/ >>>> >>>> - Nick >>>> >>>> >>>> On Thu, Oct 10, 2019 at 5:09 PM vineet daniel <vineet...@gmail.com> >>>> wrote: >>>> >>>>> Use git to clone the code within the container to fetch latest copy of >>>>> code. >>>>> >>>>> On Thu, 10 Oct 2019, 20:59 balogun tobi, <blgn...@gmail.com> wrote: >>>>> >>>>>> How does one deploy an already developed django app using Docker? >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to django...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/django-users/da969e88-ccdc-4cac-9a37-6096b3704de1%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/django-users/da969e88-ccdc-4cac-9a37-6096b3704de1%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to django...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/django-users/CAJPbAW9mQwb4%2BLOuS0-3c0W0pW3Dt_GQfMhZ%3D_ZBw%2BvnLVxuhA%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/django-users/CAJPbAW9mQwb4%2BLOuS0-3c0W0pW3Dt_GQfMhZ%3D_ZBw%2BvnLVxuhA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/django-users/CAGuvt903iPdjT%3DNu4iHun%2BkJ-O8EtH-AN7TOmhto7oShqYKsDQ%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/django-users/CAGuvt903iPdjT%3DNu4iHun%2BkJ-O8EtH-AN7TOmhto7oShqYKsDQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/ecc10a91-ca14-4c84-845d-5fed90ec12f2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/ecc10a91-ca14-4c84-845d-5fed90ec12f2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/988ea33a-95b6-45b6-b535-bfa1082ca90a%40googlegroups.com.
