Upstream KFP has hardcoded pointer to minio-service.kubeflow for object storage

[ca-scribner]

This results in kfp only being deployable to the kubeflow namespace with a service called minio-service that points to the object storage. See #387 for more background.

If we're really pedantic, kfp could probably be deployed to any namespace so long as a service minio-service existed in namespace kubeflow, but that's a hacky workaround.

[ca-scribner]

#387 patches this for charmed kubeflow so our solution currently works, but this issue will stay open until upstream has fixed this and we've updated to the new upstream (see canonical/minio-operator#151 for more details on what needs to be done upstream)

[kimwnasptd]

Linking it with canonical/bundle-kubeflow#698

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6890.

This message was autogenerated