We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This means that old data is still present when a new deployment ends up in an existing namespace.
The text was updated successfully, but these errors were encountered:
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-molgenis-mosaic-postgresql-0 Bound pvc-04a69601-458d-11e9-adaf-005056b2fdf8 10Gi RWO nfs-provisioner 8d data-mosaic-postgresql-0 Bound pvc-d7b0d747-476a-11e9-b919-005056b29192 10Gi RWO nfs-provisioner 6d13h pvc-elasticsearch Bound pvc-d784226e-476a-11e9-adaf-005056b2fdf8 10Gi RWX nfs-provisioner 6d13h pvc-molgenis Bound pvc-d785fbc1-476a-11e9-adaf-005056b2fdf8 10Gi RWX nfs-provisioner 6d13h
Sorry, something went wrong.
See helm/charts#1863
fix(molgenis): use PVC for postgres
8b299e3
Fixes molgenis#126
fdlk
Successfully merging a pull request may close this issue.
This means that old data is still present when a new deployment ends up in an existing namespace.
The text was updated successfully, but these errors were encountered: