You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pachyderm currently uploads things automatically to an AWS S3 database and maintains the data there. I notice that there is an option to route the output repo of a pipeline to a MySQL database but there isn't an option to host the entire database on a MySQL database or other alternative.
I bring this up as a security concern for people who don't want to use an outside service of a database and would prefer to host it themselves locally so that they could manage and protect their data their way. This would make pachyderm more service oriented instead of standalone.
If there is a way to accomplish this today via workaround, what does that require?
This would be a fairly simple workaround where instead of creating a pod that connects and manages a MySQL database instead of a AWS S3 gateway (There is already a POSTFRES pod in pachyderm that is used for AWS s3 connection and management and the easiest solution I could think of is to change the functionality of that)
(Optional) What is your proposal for a feature to solve this?
Environment?:
Kubernetes version (use kubectl version):
Pachyderm CLI version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
OS (e.g. from /etc/os-release):
Others:
The text was updated successfully, but these errors were encountered:
What is the goal / desired outcome?
Pachyderm currently uploads things automatically to an AWS S3 database and maintains the data there. I notice that there is an option to route the output repo of a pipeline to a MySQL database but there isn't an option to host the entire database on a MySQL database or other alternative.
I bring this up as a security concern for people who don't want to use an outside service of a database and would prefer to host it themselves locally so that they could manage and protect their data their way. This would make pachyderm more service oriented instead of standalone.
If there is a way to accomplish this today via workaround, what does that require?
This would be a fairly simple workaround where instead of creating a pod that connects and manages a MySQL database instead of a AWS S3 gateway (There is already a POSTFRES pod in pachyderm that is used for AWS s3 connection and management and the easiest solution I could think of is to change the functionality of that)
(Optional) What is your proposal for a feature to solve this?
Environment?:
kubectl version
):pachctl version
):The text was updated successfully, but these errors were encountered: