-
Notifications
You must be signed in to change notification settings - Fork 916
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
KFP 2.4.0 follow up (metacontroller) #2970
Comments
CC @hbelmiro @tarekabouzeid because right now upstream KFP multi-user is broken until we fix the metacontroller there as well. |
@juliusvonkohout when this fix will be implemented? |
@tarekabouzeid @biswassri want to work on it |
@tarekabouzeid @biswassri I did not get feedback for a week, so I created kubeflow/pipelines#11608 to at least fix the broken upstream KFP. Afterwards you can still upgrade metacontroller from 2.6.1 to 4.x |
@juliusvonkohout @tarekabouzeid Apologies, I hadn't checked email/git over the last week. So I missed this until now. I created the clean-up of the PSS patches PR #2986 since it's not dependent on the KFP sync PR. Once kubeflow/pipelines#11608 is merged in, I can check with the metacontroller upgrade. Hope that's okay. |
@juliusvonkohout apologies for that also. I was occupied last week. |
Validation Checklist
Version
master
Describe your issue
@biswassri please wait for my metacontroller fixes in #2953 to be merged and then pull from master. Afterwards with the improved tests you can try to update metacontroller from 2.6.1 to 4.x. Depending on what works we merge it in kubeflow/manifests and in any case we need to upstream to kubeflow/pipelines as well.
And please also remove the PSS patches "(no change)" that we have upstreamed from Kubeflow/manifests
Steps to reproduce the issue
Install Kubeflow
Put here any screenshots or videos (optional)
No response
The text was updated successfully, but these errors were encountered: