rh-aiservices-bu / insurance-claim-processing

Source for "Streamlining insurance claims with OpenShift AI" Lab
https://rh-aiservices-bu.github.io/insurance-claim-processing/
MIT License
32 stars 83 forks source link

pre-create the projects #150

Closed erwangranger closed 5 months ago

erwangranger commented 6 months ago

for each user (user1 - userX):

then

RHRolun commented 5 months ago

@erwangranger is there any benefit of deploying minio in each rather than using the shared minio? I'm asking cause I have to call the data connection "Shared Minio - pipelines" even for the automatically created users (with their own minio) with their own minio so that the secret looks the same for the pipelines.

erwangranger commented 5 months ago

I can't think of any major benefit. 1 minio with 60 buckets, vs 60 minio with one bucket. Results are mostly the same, but with a lot more pods.

The shared minio has been solid for us, so we could keep that part unchanged. Also, if users were doing this "the long way", manually, we'd need to provide them instructions for Minio as well.

I'd say, for now, we can limit it to just creating the Data Connection to the shared minio, and keep a single Minio. I'm ok with that.

RHRolun commented 5 months ago

Closed with https://github.com/rh-aiservices-bu/insurance-claim-processing/pull/180