This message was deleted.

Hey Matthew, about the 2. question , the following should work: • Create a directory

I10n

under your

pkg/<EXTENSION>

• Inside that directory create a

en-us.yaml

with the following content:

cluster:
  provider:
    oxide: Oxide

Short explanation: • The name you see appear here comes from the internationalization mappings (these can be language-specifc), and BTW, you might need internationalization for field names inside your

cloud-credentials

part of the extension. • Why does it show

oxide

out-of-the-box ? That’s actually your Node Driver’s unique name for Rancher.

Thank you! I received similar information in https://rancher-users.slack.com/archives/C04PPGWAWNR/p1741114487535009 and I updated our extension repository with this here: https://github.com/oxidecomputer/rancher-ui-extensions-oxide/blob/main/pkg/oxide/l10n/en-us.yaml However it was mentioned this may change in the future. Is that true? At first I tried to update the information in the

NodeDriver

CRD but that was unsuccessful so I appreciate that it can be done with translations. Just for my curiosity is the out-of-the-box ID determined via the CRD or something else?

About a possible change in the future, I cannot say for sure! Maybe @stocky-account-63046 can help. As for ID, it comes actually from the binary name, NOT the CRD (which is a bit weird…). It is a pleasure for me too to have met you guys at SUSECON, you guys are doing very exciting stuff!

Perfect! Thank you so much. This is really helpful.

👍

RE localisation of provider name, i don't think we have plans to change and it's documented publicly https://extensions.rancher.io/extensions/next/advanced/provisioning#localisation