Skip to content
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

feat(backend): Upload namespaced pipeline definitions. Part of #4197 #8511

Conversation

elikatsis
Copy link
Member

Description of your changes:
This is the backend part pushed by #8196. See the aforementioned PR and the linked issued for details.

This PR is part of the overarching idea to support namespaced pipeline definitions.
The whole idea is thoroughly analyzed and exposed in this design doc: https://docs.google.com/document/d/1fM4y2L1IVqVj-iiNjYFRRktdCh7FQXgU2XpaYLaqt-A/edit?resourcekey=0-kd5loyP7w3PBD0ug6ECmLQ#

Objective of this PR is to:

  1. Fix backend authentication for upload requests in order to properly authenticate users to upload pipeline definitions in specific namespaces
  2. Update the swagger definitions accordingly for the upload APIs and generate the code for the relevant clients

Part of #4197

Checklist:

Fix the way KFP API server authenticates pipeline upload requests.
We leverage 'isAuthenticated()` function which requires proper
initialization of the context object to include user identity.
Extend swagger defintion of the pipeline upload API with a namespace
parameter in order to support uploading namespaced pipelines.
Autogenerate the Go and Python clients after extending the swagger
definitions of upload pipeline APIs with a namespace field.
@elikatsis
Copy link
Member Author

elikatsis commented Nov 30, 2022

/cc @chensun @zijianjoy @jlyaoyuli @Linchin @juliusvonkohout @StefanoFioravanzo
to get your attention in the backend PR. This PR as well as the kfp-server-api release after this merge block the SDK PR (#8512).

@juliusvonkohout
Copy link
Member

@elikatsis i strongly suggest putting this on the agenda for the next KFP meeting. As you have seen the previous PR only got attention after i did that.

Copy link
Member

@chensun chensun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@juliusvonkohout
Copy link
Member

juliusvonkohout commented Dec 1, 2022

@elikatsis run-frontend-integration-tests failed in kubeflow-pipeline-e2e-test

 integration-test-rmnf9-3207874327: 20 passing (57.60s)
integration-test-rmnf9-3207874327: 2 failing
integration-test-rmnf9-3207874327: 
integration-test-rmnf9-3207874327: 1) deploy helloworld sample run displays run inputs correctly:
integration-test-rmnf9-3207874327: run message is not shown correctly
integration-test-rmnf9-3207874327: running chrome
integration-test-rmnf9-3207874327: AssertionError [ERR_ASSERTION]: run message is not shown correctly
integration-test-rmnf9-3207874327:     at Context.it (/src/helloworld.spec.js:173:12)
integration-test-rmnf9-3207874327:     at new Promise (<anonymous>)
integration-test-rmnf9-3207874327:     at new F (/src/node_modules/core-js/library/modules/_export.js:36:28)
integration-test-rmnf9-3207874327: 
integration-test-rmnf9-3207874327: 2) deploy helloworld sample run shows logs from node:
integration-test-rmnf9-3207874327: Promise was rejected with the following reason: timeout
integration-test-rmnf9-3207874327: running chrome
integration-test-rmnf9-3207874327: Error: Promise was rejected with the following reason: timeout
integration-test-rmnf9-3207874327:     at element("#logViewer") - index.js:312:3 

@gkcalat
Copy link
Member

gkcalat commented Dec 1, 2022

/retest

@google-oss-prow google-oss-prow bot merged commit 931c14a into kubeflow:master Dec 1, 2022
@elikatsis elikatsis deleted the feature-pangiann-upload-namespaced-pipelines-backend branch December 2, 2022 09:47
jlyaoyuli pushed a commit to jlyaoyuli/pipelines that referenced this pull request Jan 5, 2023
…ow#4197 (kubeflow#8511)

* feat(backend) Fix authentication in upload requests

Fix the way KFP API server authenticates pipeline upload requests.
We leverage 'isAuthenticated()` function which requires proper
initialization of the context object to include user identity.

* feat(backend): Add namespace field in pipeline upload swagger definition

Extend swagger defintion of the pipeline upload API with a namespace
parameter in order to support uploading namespaced pipelines.

* chore(backend): Generate Go & Python clients

Autogenerate the Go and Python clients after extending the swagger
definitions of upload pipeline APIs with a namespace field.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants