opendatahub-io/architecture-decision-records

Collection of Architectural Decision Records

architecture-decision-records's Issues

[Questions] Regarding Data Science Pipelines

Hi all!
It's amazing that we can actually look up the ADRs in this repository! Thanks a lot for the openness! 🙏

I was going through this one: https://github.com/opendatahub-io/architecture-decision-records/blob/main/ODH-ADR-0002-data-science-pipelines-multi-user-approach.md
and I have some follow-up questions, I hope this is the right place 🙂

integrating Data Science Pipelines (upstream = Kubeflow Pipelines)

Here I read that Kubeflow is the technology to be used, is it a requirement? An assumption? Or have we evaluated alternatives and decided to use Kubeflow? In the latter case, I'm super interested in having access to the comparison!

we propose to roll out multiple individual single-user Kubeflow Pipelines stack into multiple namespaces

On the Kubeflow documentation, I can find that the minimum requirements are pretty significant, do we have estimations of the system requirements in the proposed configurations(e.g. shared vs. local minio and postgres) and adding the operator needs? how much do we expect this to scale on a user's cluster? Have we explored alternatives or do we expect the users to use a single installation in a dedicated namespace on each cluster? - I think that answers to these questions are relevant information that should validate the decision taken.

Thanks a lot in advance!

Request: Rename repo to "architecture-decision-records"

ADR isn't immediately obvious to someone what this repo is based on the name.

It would be great to rename this to the non-abbreviated name to make it more understandable what this repo is directly from the GitHub repo list.