Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable mounting of a shared PVC into multiple deployments #469

Closed
zsinnema opened this issue Mar 22, 2022 · 0 comments · Fixed by #470
Closed

Enable mounting of a shared PVC into multiple deployments #469

zsinnema opened this issue Mar 22, 2022 · 0 comments · Fixed by #470
Assignees
Labels
enhancement New feature or request new feature
Milestone

Comments

@zsinnema
Copy link
Contributor

For some applications it would be really nice if we could mount a "shared" PVC into multiple deployments.
There are apps where the frontend and the backend are different deployments. E.g. the frontend is a NXING serving a static react app and the backend is a Flask/Django server.

For user content (uploaded content) the application would benefit from sharing a PVC between the frontend and the backend.
The backend will store the uploaded content (e.g. file) and the frontend will serve the file back to the user.

We can do this by adding a volume object to the harness.deployment of the microservices. The issue is that when I have 2 or more services the PVC is multiple times created.

solution proposal:
add the attribure auto to the harness.deployment.volume object.
when true: create the PVC
when false: don't create the PVC

@zsinnema zsinnema self-assigned this Mar 22, 2022
@zsinnema zsinnema added this to the v1.0.0 milestone Mar 22, 2022
zsinnema added a commit that referenced this issue Mar 22, 2022
@zsinnema zsinnema added enhancement New feature or request new feature labels Mar 22, 2022
filippomc added a commit that referenced this issue Mar 22, 2022
#469 feature: enable application volume to be shared across multiple different deployments
zsinnema added a commit that referenced this issue Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new feature
Projects
None yet
1 participant