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

chore: integrate 2.2.0 rocks #520

Merged
merged 9 commits into from
Jul 9, 2024
Merged

chore: integrate 2.2.0 rocks #520

merged 9 commits into from
Jul 9, 2024

Conversation

orfeas-k
Copy link
Contributor

@orfeas-k orfeas-k commented Jun 20, 2024

@DnPlas
Copy link
Contributor

DnPlas commented Jul 4, 2024

Re-running the CI because the error is a known issue with building a dependency package and it should not be related with the changes in this PR.

Copy link
Contributor

@DnPlas DnPlas left a comment

Choose a reason for hiding this comment

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

Thanks @orfeas-k !

Just a super minor comment, other than that LGTM.

I have done the following to ensure the charms and workloads are working as expected:

Env

microk8s: 1.29-strict/stable
juju: 3.4/stable (3.4.4)
addons: dns hostpath-storage metallb:10.64.140.43-10.64.140.49

Testing steps

  1. Deploy CKF from latest/edge juju deploy kubeflow --channel latest/edge --trust
  2. Refresh kfp-operators to this PR e.g. juju refresh kfp-api --channel latest/edge/pr-520
  3. Because charming-actions/upload-charm action is uploading images incorrectly and affecting charms' functionality bundle-kubeflow#962 is affecting the release job, I had to manually update the oci-image of all charms juju refresh kfp-api --resource oci-image=<image from this PR>
  4. Waited for everything to settle and created runs and experiments.
  5. Everything seems to be working fine (runs are scheduled and executed, artefacts are accessible, experiments and runs can be created). The only thing that is not working is recurring runs because of KFP Recurrings Runs not working on kubeflow 1.8 #517, but it should be fixed by Change namespace in kfp-schedwf #529 for latest/edge.

Copy link
Contributor

@DnPlas DnPlas left a comment

Choose a reason for hiding this comment

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

Thanks @orfeas-k !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants