Alexla/upgrade kfp v1.8.16 #23
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ubeflow#6804) * Use google.protobuf.Value in v2 for passing parameters. * retest samples. * Fix tests. * Update release, more cleanup. * Use github.com/kubeflow/pipelines/api from same repo. * Run go mod tidy * chore: go mod tidy * fix v2 compile error and clean up unused code * pr comments. * update goldens * Fix metadata recording. * Update kfp mlmd client. * fix test again * another try. * chore: migrate v2 DAG driver input parameters to protobuf.Value + small refactorings * fix v2 launcher + clean up * fix a compile error * fix a few more tests * fix number parsing * clean up * disable cache_v2 test. Co-authored-by: Yuan Gong <[email protected]>
* feat: upgrade argo to v3.1.14 * go mod tidy * fix license versions
PiperOrigin-RevId: 406246359
…#6825) * Implement experimental `@component` component * release note
…Protobuf.Value for import uri. (kubeflow#6827) * fix importer * release note * remove error usage in test sample * disable importer test
* added draft of create v2 pipeline run * fixed broken UT and added UT for parsing template * modified run apis to support v2 IR spec * remove temporary patch * fixed dependency * fixed build failure * finished draft * finished create job and run * refactor template and fixed broken UT * updated go license * fixed build failure * fixed build * added UT * modified UT * fixed build failure * fixed license
* feat(sdk): add load_component_from_* * address comments' : * update release notes
…nent PiperOrigin-RevId: 406292369
* fix display name for experimental tasks_group * release note
* chore(sample): Update Katib examples for 0.12 release * Run Early Stopping example
* feat(frontend): Allow setting AWS_S3_ENDPOINT Allows setting the S3 endpoint used by minio to allow regions other than us-east-1 * feat(frontend): allow to configure s3 bucket region for artifacts * fix formatting * add integration test for non-default s3 bucket region
…r 0.1.9 release PiperOrigin-RevId: 406876964
…eflow#6649 (kubeflow#6622) * Update view-edit-cluster-roles.yaml * Update view-edit-cluster-roles.yaml
…tform/ folder. The image is not specific to aiplatform component. PiperOrigin-RevId: 407182304
maxNumViewers is per namespace not entire cluster. [This PR](https://github.com/kubeflow/pipelines/pull/1623/files#diff-36da225a16f9c6742cee006c2554b6ef6836c9ab2b509a5169b5d3a4acc36977) changed the scope from cluster to namespace.
…pes bidirectionally (kubeflow#6859)
…low#6864) * Update RELEASE.md * Update __init__.py
This change includes: - Renaming custom job op - Moving it to a utils module. - Removing workerpoolspec override from the interface. - Updating the sample for custom_job PiperOrigin-RevId: 407603075
* chore(deps): Upgrade google-cloud-storage to v2 * Update RELEASE.md
…flow#7780) * add README with project description * modify language * add links for python code and yaml
* expand accepted typing extensions versions * update release notes
…==1.8 (kubeflow#7875) * use kfp-pipeline-spec>=0.1.16 * add functions to v2 compiler utils * add v2 compiler utils tests * implement retry policy compilation logic * add v2 compiler tests * add retry policy sample test * add release note
* bump version * update release notes * Update RELEASE.md Co-authored-by: Chen Sun <[email protected]>
* add IteratorPolicy to v1 pipeline_spec proto * revert proto changes as it is unnecessary * bump pipeline_spec dependency to 0.1.16 * add compiler support for parallelism in ParallelFor * added unit tests * add one more test case * add compiler cli tests for parallelfor with parallelism setting * restore change to pipeline spec * address PR comments: revert parallelism default to None, update error message, update tests * update compiler_tests golden * fixed function signature, simplified test function args * add release.md message
* update README example * use keyword arguments
…low#8226) * add support for dynamic importer metadata * fix non-deterministic dict comprehension processing * use util function
* bump version * update release notes
…w users to skip docker build. Fixes kubeflow#8382 for 1.8 (kubeflow#8383)
…ubeflow#8454) * fix multiple workers bug on gcsfuse error * add comment for context
* bump version * update requirements.txt
* bump version * update release notes * be more precise in release notes
…8473) * more google auth changes * update release notes
…kfp-v1.8.1 Kubeflow Pipelines 1.8.1 release
To be honest I haven't yet, was going to pick folks brains on the best way to proceed here. I've got a PR for the
I got these from the list of artifacts |
I am not sure 100% where this kfp client gets used but I would imagine any case that uses it. So specific projects that use this. If the case gets validated in integration tests then maybe that works. |
|
Blocked on Kserve upgrade to at least v0.9.0 due to non-overlapping constraints for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes:
Pull in upstream changes from v1.8.16 to get us closer to the latest version!
We use v1.8.16 because this aligns with the major+minor KFP version that ships with KFP v1.5.0 (see here, it's
v1.8.1). We don't want to usev1.8.1directly as this PR is trying to addresspythondependency conflicts in thezillow-kfpSDK so the additional patch versions include requirements changes to make KFP compatible with the remainder of thepythonecosystem it depends on.Checklist: