Hello rancher teams, I have a question. When I check the Account and API Keys page, I see that there are many kubeconfigs that have been generated previously. My question is: why do some kubeconfigs show a "Scope" while others display a dash (-) instead? What causes the "Scope" to appear as a dash when generating a kubeconfig? I would like each kubeconfig to include its Scope so that I can easily identify which cluster it belongs to. Is there a way to configure or set this behavior?

@ancient-dinner-76338 You have to select a scope while creating cluster.

@few-plumber-96374 That’s not exactly my question. For example, when I click the copy button here, the kubeconfig is automatically added to the list on the Account and API Keys page. When I check that page, sometimes the scope is shown correctly, but other times it just shows a dash (-). So my question is: why do some kubeconfigs have a scope of "-"? From what I understand, what you described above isn’t generating a kubeconfig, but rather just creating a regular token.