Test 1.8/stable with juju 3.5

[DnPlas]

Context

To make sure this issue is not affecting other charms, we must check the services of the charms that are using ROCKs to identify issues.

What needs to get done

1. Deploy 1.8/stable with juju 3.5
2. Review the services that could be affected by the mentioned issue
3. Report back any discoveries

Definition of Done

The 1.8/stable CKF bundle is tested against juju 3.5 and a report with potential issues is posted in this issue.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

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

This message was autogenerated

[DnPlas]

I ran manual and UAT tests on top of 1.8/stable and can confirm that the mentioned issue is not affecting 1.8/stable as long as we don't promote the kubeflow-dashboard from 1.8/edge to 1.8/stable.
For now, the best workaround that we have to prevent any issues with it is to use the upstream image temporarily in both main and track/1.8.