Test the upgrade path from CKF 1.8 to latest/edge (1.9)

[kimwnasptd]

Context

Start testing the upgrade from CKF 1.8 to 1.9, by doing the upgrade to latest/edge.

What needs to get done

1. Deploy CKF 1.8
2. Prepare a document with all the steps for upgrading to latest/edge
3. Create issues on the way, with anything that blocked us

Definition of Done

1. We have a document that tracks the steps for the upgrade, or a list of issues that blocked us

[syncronize-issues-to-jira[bot]]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5757.

This message was autogenerated

[DnPlas]

This document will have to include the following information:

• Some versions of istio require k8s >= 1.26 for upgrading, which means users/customers will have to make sure that happens. See https://github.com/canonical/istio-operators/issues/413#issuecomment-2146960491 for more info.
• mlmd migration path as defined in https://github.com/canonical/mlmd-operator/issues/74.

[orfeas-k]

(if approved)

• Adding the new relation between katib-controller and katib-db-manager due to https://github.com/canonical/bundle-kubeflow/pull/922 https://github.com/canonical/katib-operators/pull/185

[misohu]

Note for release notes

In this PR https://github.com/canonical/notebook-operators/pull/372 we are adding config options to notebook controller

• cluster-domain: Specifies the base domain name of the Kubernetes cluster, which is used in culling to correctly resolve and address the services and resources within the cluster.
• cull-idle-time: The amount of time (in seconds) that a Jupyter notebook server can remain idle before it is automatically shut down.
• idleness-check-period: Interval (in minutes) at which the system checks for idle Jupyter notebook servers to determine if they should be culled.