-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline minio artifact secret - named mlpipeline-minio-artifact; workflow expects minio-artifact #193
Comments
* Update argo artifact repo secret name This is to align with https://github.com/kubeflow/kubeflow/blob/8a01606dc43b217a221eaf2fea2a8207d72ad75d/kubeflow/argo/prototypes/argo.jsonnet#L13 Fix #193 * Update argo-base_test.go * Update argo-overlays-istio_test.go
Hi @IronPan I am still getting this on GCP running from OSX, did you ever get a fix for this? Here's the error in the pod:
|
I got the same error, the reason is secret I found a temporary fix in this comment |
I tried running the pipelines sample exit on run and the containers failed to start.
I have a secret named "mlpipeline-minio-artifact"
My guess is kustomize is adding mlpipeline as a common prefix.
We recently upgraded the pipelines to the latest image. Not sure if that changed things.
The text was updated successfully, but these errors were encountered: