-
Notifications
You must be signed in to change notification settings - Fork 885
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
Kubeflow 1.9 follow up: Upstream our authorizationpolicy and oauth2-proxy changes to kubeflow/pipelines and kubeflow/kubeflow #2804
Comments
We also need to decide on the jupyterlab example image tags "One thing i noticed is that since #2781 the example Jupyterlab and vscode images are still on the latest tags. I do not think that this is a blocker since they are example images and it is what is upstream in kubeflow/kubeflow (maybe by mistake). Nevertheless I will create a follow up issue." |
@juliusvonkohout I'm not sure I understand the problem the issue tries to expose. Is it about the tag used by the example notebook images? And then what is the problem you expose about the authorization policies? |
@kimwnasptd we have additional stuff in the upsteam folders from kubeflow/kubeflow and kubeflow/pipelines. This will break on the next synchronization step. See also the comments in #2815. Just try yourself to synchronize with the https://github.com/kubeflow/manifests/blob/master/hack/synchronize-pipelines-manifests.sh and https://github.com/kubeflow/manifests/blob/master/hack/synchronize-kubeflow-manifests.sh and verify that essential stuff is being deleted. For example the requestprincipal in the pipeline autorizationpolicy or the oauth2-proxy overlay for the central dashboard. And all tags for Kubeflow/kubeflow will switch from 1.9.0 to latest. |
Ah I see, so it's about manifest syncing from other repos and not overriding the I can see 2 ways but let me know which you think is more feasible:
|
let me merge first #2815 and we should upstream at least the kubeflow/pipelines authorization policy with the requestprincipals as soon as we can. |
kubeflow/pipelines#11347 is probably the last item |
Validation Checklist
Version
master
Describe your issue
Follow up of
#2795
And
#2753
And
#2734 (comment)
@kimwnasptd @rimolive
Steps to reproduce the issue
Stuff will break on the next manifest synchronization for Kubeflow/pipelines and kubeflow/kubeflow
Put here any screenshots or videos (optional)
No response
The text was updated successfully, but these errors were encountered: