This message was deleted.
# general
a
This message was deleted.
a
Hello @few-plumber-96374, @creamy-pencil-82913, @stocky-account-63046. Could you help answer this question?
f
@ancient-dinner-76338 You have to select a scope while creating cluster.
a
@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.
Solved, by enable authorized cluster endpoint now every generate kubeconfig in Account and API Keys page will show scope (clusterId)
🙌 1