Skip to content

Conversation

@sduvvuri1603
Copy link
Contributor

Description of your changes:

  • Added the pipeline_run_parallelism field in PipelineConfig (proto, Go/Python bindings, DSL, compiler) and plumbed it into the generated workflow bundle and Kubernetes platform spec.
  • Updated backend logic to persist the value in kfp-pipeline-config, apply it to Argo spec.parallelism, and covered it with TestCreateRun_PipelineRunParallelismConfigMap; regenerated proto goldens.
  • Refreshed docs and sample pipeline (pipeline_with_workspace.py/.yaml), verified the compiled output includes pipelineRunParallelism: 3, captured before/after runs showing the ConfigMap entry, and confirmed the field in the compiled workflow YAML via the DSL compiler.

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chensun for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@google-oss-prow
Copy link

Hi @sduvvuri1603. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sduvvuri1603 sduvvuri1603 force-pushed the feature/pipeline-run-parallelism branch 2 times, most recently from 99f2fc8 to d34a1b2 Compare November 12, 2025 21:22
@alyssacgoins
Copy link
Contributor

/retest

@sduvvuri1603 sduvvuri1603 force-pushed the feature/pipeline-run-parallelism branch 5 times, most recently from 73f3a0a to 693e908 Compare November 14, 2025 19:30
@sduvvuri1603 sduvvuri1603 force-pushed the feature/pipeline-run-parallelism branch from 8a727b1 to f2940e2 Compare November 14, 2025 19:38
@sduvvuri1603 sduvvuri1603 force-pushed the feature/pipeline-run-parallelism branch from 82756e1 to 60a35d8 Compare November 14, 2025 21:27
@google-oss-prow
Copy link

@sduvvuri1603: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@hbelmiro
Copy link
Contributor

/ok-to-test

@hbelmiro
Copy link
Contributor

/retest

@sduvvuri1603 sduvvuri1603 marked this pull request as ready for review November 17, 2025 17:06
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.

3 participants