Julius von Kohout comments

Results 653 comments of


                                            Julius von Kohout

fix(backend): set correct permissions for local directory

/ok-to-test

fix(backend): set correct permissions for local directory

is this related to https://github.com/kubeflow/pipelines/pull/6530 and https://github.com/kubeflow/pipelines/issues/5673 ?

fix(backend): set correct permissions for local directory

@zijianjoy this is important for the 2.0 release then, because otherwise it would be a regression.

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

@chensun @zijianjoy @jacobmalmberg @ca-scribner i finally have something that is worth merging for namespace isolation. It is also quite easy to test on your own instances, because i only changed...

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

/assign @zijianjoy

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

@chensun can you provide some feedback? I will happily implement any changes if needed.

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

@zijianjoy The minio mc license was changed quite late https://github.com/minio/mc/commit/1402987ccbb9877e15d865a110a21a9518ec9e44 so that should be fine. We are using a way older mc, exactly the same date as your current minio-license-compatible...

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

By the way @Bobgy proposed exactly such a lifecycle policy here https://github.com/kubeflow/pipelines/issues/6204#issuecomment-903011330

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

@TobiasGoerke is this what you also have in mind for artifact isolation?

feat(backend): isolate artifacts per namespace/profile/user using only one bucket

As desired i moved it into its own distribution because gcs and aws will need different settings. So far this only works for minio. I hope that is fine with...