[Tracker] Dashboard to Support Operator Rework

[andrewballantyne]

Description

The ODH Operator is getting a rework. We are losing access to KfDefs in favour of a CRD. There will be migration involved in no longer handling some resources in the Dashboard and those will be moved to other components. This will be a longer effort to support isolated functionality and not make the Dashboard a dumping ground for support.

Target Branch

main - This was directly put into main as it was needed for initial support. This will not need incubation.

Requirements

• Support of the v2 Operator in the Dashboard
  • KfDef => DSC CR

Itemized UX Issues

N/A

Itemized Dev Issues

• [Investigation]: Operator Support #1909
• [Story]: Remove KF Watcher Crash on no KFDef Installed #1508
• [Story]: Remove reliance on KfDefApplications OdhApplication CR field #1510
• [Feature Request]: Add support for DataScienceCluster CR in dashboard. #1491
• [Story]: Support pulling DSC Status #1979
• [Operator V2] Access to DS Projects fails if DS Pipelines are disabled from DSC #1870

Related artifacts

No response

[andrewballantyne]

We won't complete this for this sprint... we will address the initial issue with Pipelines locking down the Dashboard Project UI (#1870) but not the more improved usage of ignoring feature flags when the component is off (#2010).

[andrewballantyne]

Basic support for the Operator has been done and #2010 has been moved to a feature enhancement for next sprint.

We will be closing this tracker as it has completed the basic goal it set out to do which was not crash when using the v2 operator and still offer the same features.

Due to the nature of the v2 Operator, our feature flags will need to be disabled if the backing component is not there. This will be improved by the 2010 issue noted earlier.