Closed steverfrancis closed 1 month ago
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This is actually a bug in kubeconfig
generation that we need to fix (the cluster name itself of "1.3" should be fine).
Bug Report
talosctl gen config will accept a cluster name of "1.3", but this fails to create a valid cluster as its of type numeric.
Description
Logs
Environment
talosctl version --nodes <problematic nodes>
]kubectl version --short
]