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]

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 Update istio-operators istio-operators#413 (comment) for more info.
• mlmd migration path as defined in Write migration documentation from podspec to sidecar mlmd-operator#74.

[orfeas-k]

(if approved)

• Adding the new relation between katib-controller and katib-db-manager due to chore(latest): Add katib-controller katib-db-manager relation #922 fix: Introduce k8s-service-info between katib-controller and katib-db-manager katib-operators#185

[misohu]

Note for release notes

In this PR canonical/notebook-operators#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.

[orfeas-k]

Closing with document https://docs.google.com/document/d/1Wg32O5PF8RMy7ng7hY9gX37lHnwmszyBt4D2lI_MSjQ/edit#heading=h.gkp9mi5dbjw