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.
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 https://github.com/canonical/minio-operator/pull/151 for more details on what needs to be done upstream)
This results in kfp only being deployable to the
kubeflow
namespace with aservice
calledminio-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 namespacekubeflow
, but that's a hacky workaround.