StarlingX isolcpus resource reported as "windriver.com/isolcpus"

[Chris Friesen]

Currently in StarlingX the custom isolated CPUs resource is reported as "windriver.com/isolcpus". It should really be something like "starlingx.io/isolcpu".

Severity: Minor

Steps to Reproduce:
Configure isolated CPUs via "system host-cpu-modify", then run "kubectl describe node <hostname>" to see the isolated CPU resources.

Expected Behavior:
Should use the starlingx name for upstream code rather than windriver.com.

Actual Behavior:
Uses windriver.com as the resource name in starlingx.

Reproducibility:
Reproducible

The complicating factors are that we can't break existing customer applications which are using the windriver.com/isolcpus resource name.

A possible fix would be to modify the system to accept both names for one release and deprecate the windriver.com/isolcpus resource name, forcing users to switch to the starlingx.io/isolcpu resource instead. For the release where we support both, this would require the system to handle the resource accounting for both resource types if either one was consumed.

[Ghada Khalil (gkhalil)]

screening: low priority / not gating issue, but should be considered for a fix.