[Bug]: Support v1alpha1 of AcceleratorProfiles

[andrewballantyne]

Is there an existing issue for this?

• I have searched the existing issues

Deploy type

Installing Dashboard directly (eg. v2.12.0, commit xyz, branch name)

Version

incubation

Current Behavior

We do not support existing clusters that use v1alpha1 version of the AcceleratorProfile CRs.

We migrated our AcceleratorProfile CRD to v1 in main for our stable release when we put together the official release of AcceleratorProfiles & Habana support. However we didn't consider existing installations that are using v1alpha1.

Expected Behavior

We need to support v1alpha1 (same value as v1) in the CRD & write a migration script into the backend at pod startup to convert them to v1.

This effort will have to stay at least until we write the admin view.

Steps To Reproduce

1. Create v1alpha1 AcceleratorProfile (you'll need an older CRD)
2. Upversion the CRD and drop v1alpha1 support

Workaround (if any)

Delete all the resources and migrate manually.

What browsers are you seeing the problem on?

No response

Anything else

No response

[andrewballantyne]

Upping the priority of this to reflect the need to close it out before the next release.