Fleet addon provider doesn't have ProviderName set

[thehejik]

After installing Turtles Operator v0.10.0 with Seamless integration with Fleet and CAPI enabled (installs caapf v0.3.0) together with UI extension in Rancher v2.8 there is no ProviderName set for fleet addon in CAPI/Providers overview page. This field seems to be mandatory when adding a custom provider manually. It probably doesn't have any impact on functionality.

What did you expect to happen?

The ProviderName is set for eg. to fleet value.

How to reproduce it?

No response

Rancher Turtles version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug

[Danil-Grigorev]

Unfortunately this is upstream table representation limitation. If it is not set, it means that the name is consistent with providerName internally. If there is a way to represent default for jsonPath, this issue is hard to fix.

[alexander-demicev]

@Danil-Grigorev any chance we can introduce custom provider names if fetch config is provided?

[Danil-Grigorev]

Not sure I understand the question.

Custom provider naming is possible now, and the table viewed in UI shows providers with custom name. It is determined based on spec.providerName being set or not. Missing spec.providerName uses metadata.name as a source for provider name internally.

The only provider wich has no custom name is the fleet addon provider. To address the display issue, I propose to change table representation to use a new status.providerName field, which will be populated by controller from either of the sources:

• metadata.name
• spec.providerName (has higher priority)