-
Notifications
You must be signed in to change notification settings - Fork 53
Privileged option for Deis Apps #450
Comments
This sounds contrary to 12factor-- which is where the workflow focus is. In a 12factor app, you would never mount a file system. Instead you'd use backing services to handle persistent storage. I'm not saying every app someone might want to deploy adapts well to that methodology, but for such apps, I believe the best way to handle is to "drop down" to k8s and handle it there, rather than by broadening the scope of workflow. |
related to @krancour's discussion: deis/deis#231 |
We should leverage k8s volumes in v2 and yes not every Web App can follow 12factor, but these btw that stopped of using Deis in my previous work |
@krancour what kind of backing services you are talking if e.g. some files need to be access for read/write in Deis App? |
Please see other discussions related to this topic, where we have discussed this and given the reasons against it until we implement deis/deis#231: deis/deis#4907 The idea is to use S3 credentials (or Ceph, Swift, w/e) to read/write to persistent storage. Eventually when we implement service gateways, the gateways will provide a way to connect to persistent storage, but it'll be done in a similar fashion as recommended today. I know that when we eventually implement service gateways, if we can do it in a similar fashion to Cloud Foundry we can leverage gateways like https://github.com/hpcloud/stackato-service-filesystem to handle this for us, but any "crutch" we come up with now is not going to be the right way to solve the problem. The gateway will receive a request for a new resource, which then it will provide us a private key, username and hostname in environment variables to mount the filesystem. |
thanks @bacongobbler :) |
@bacongobbler how do you dig up related issues so fast!?! |
@krancour he has a chip in his head :) |
^^ On a more serious note, I was part of those discussions, and keywords like wordpress, drupal, and "legacy apps" will all point to those issues. It's generally the same question popping up again in another form. :) @rimusz did my explanation give you a way to explain to users how to connect to persistent storage, and shall we close this in favour of deis/deis#231 as the actionable item? |
@bacongobbler we can close this one For now I can tell only one thing for v2 Deis users, v2 supports only stateless Apps, the stateful part needs to run on Kubernertes side |
feat(docs): add documentation for limits
Would be handy to have the privileged option, as currently there is no support for persistent storage.
The privileged mode would allow to use NFS/CIFS/GlusterFS clients to mount remote volumes inside containers
The text was updated successfully, but these errors were encountered: