-
Notifications
You must be signed in to change notification settings - Fork 12
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-operators
upgrades from 2.0.0-alpha.7 -> 2.0.3 for CKF 1.8 release
#362
Conversation
* feat: add sa token component to kfp-persistence The kfp-persistence charms needs a ServiceAccount token to be inside the workload container to be able to start the service. The sa token component will generate the required token and save it in a file where it can be accessed to later be pushed from the charm to the workload container. Fixes #343 * tests: use mysql 8.0/stable for integration tests
* fix: apply authorization policy with relaxed rule
* refactor: refactor env variables for kfp-api to match v2.0.2 For a few releases the KFP API server component has been defining certain configurations using env variables instead of a config file. This change plus adding/removing vars will ensure the charmed kfp-api keeps consistent with the upstream project.
* chore: update kfp-operators 2.0.0-alpha.7 -> 2.0.2 Update all resources according to the pipelines 2.0.2 upstream project. Signed-off-by: Phoevos Kalemkeris <[email protected]> Co-authored-by: Daniela Plascencia <[email protected]>
…nv var (#361) The METADATA_GRPC_SERVICE_HOST env var has to include the name and namespace of the metadata grpc server, otherwise pipeline runs end in errors when trying to write in the metadata SQLite DB. This commit reverts a change introduced by canonical/kfp-operators#3312.
We implement a sync.py file from upstream which we lightly modify. This commit reformats that sync.py to be as similar as possible to upstream's sync.py for easier comparison and maintenance. #331 previously reformatted sync.py to meet our style guide, but that made it harder to track and changes upstream and import them into our version This should have no functional change on the charm, it only changes things to make maintenance easier.
* update kfp-api's apiserver configuration This: * removes deprecated `DBCONFIG_USER`, etc, environment variables (they have been replaced by variables of name `DBCONFIG_[driver]CONFIG_*`) * adds `OBJECTSTORECONFIG_HOST`, `_PORT`, and `_REGION`, which previously were required. Although currently they seem to be ignored due to kubeflow/pipelines#9689 - but in theory they'll matter again? Not sure exactly the scope of that issue.
…sts (#364) * chore: updates the test bundle definitions and use latest/edge for tests This commit updates the many bundle defintions in tests/integration/bundles/ to match the latest changes to the repository. At the same time it changes the bundle that is used for running repository level integration tests from 1.7/stable to latest/edge to be able to test the kfp-operators and all other related charms with the latest changes.
* tests: enable bundle functional tests for v2 compiled pipelines The recent upgrades in kubeflow pipelines introduced a new version of the SDK that is compatible with the newer backend (pipelines 2.0.3). This commits ensures that the CI tests both a pipeline v1 and v2 to ensure good coverage.
1572e69
to
207ddfe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All changes have been reviewed in their corresponding PR. Also, the commit we 're merging to main
has been tested as part of PR #383.
A slight note, I think we could add a cleaner name to the PR
* fix: reduce flakiness of kfp-api integration tests use mysql-k8s from 8.0/stable branch instead of latest/edge
1.8-updates-dev-branch
into main
kfp-operators
upgrades from 2.0.0-alpha.7 -> 2.0.3 for CKF 1.8 release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything was also tested as it was landed in the dev branch. lgtm!
This PR merges
1.8-updates-dev-branch
intomain
, which includes changes for (but not limited to):Testing instructions
Tesnting environment:
juju deploy ./ckf-1.8-dev.yaml --trust
apiserver
is up and readyPlease note both CI tests and manual test should pass before we merge this PR.
Test bundle
ckf-1.8-dev.txt