This message was deleted.
# rancher-desktopa
adamant-kite-43734
10/14/2022, 9:40 PMThis message was deleted.
f
fast-garage-66093
10/14/2022, 9:55 PMIt means that in your
~/.kube/configkind-argokubectlhelmfast-garage-66093
10/14/2022, 9:55 PMOr you would just get an error if that cluster was created a long time ago and no longer exists.
fast-garage-66093
10/14/2022, 9:56 PMYou can switch the context either using the Rancher Desktop tray icon, or from the commandline with
Copy code
kubectl config use-context rancher-desktopn
numerous-night-87848
10/14/2022, 10:00 PMGotcha. Thanks!
numerous-night-87848
10/14/2022, 10:01 PMFrom a usability perspective, it would be great to either have that hint in the warning itself or perhaps a link to a FAQ or documentation on the rancher desktop site.
f
fast-garage-66093
10/14/2022, 10:01 PMI know; just about to copy your feedback to a thread about it. đŸ™‚
n
numerous-night-87848
10/14/2022, 10:01 PM(well, at least for us newbies đŸ™‚ )
numerous-night-87848
10/14/2022, 10:02 PMCheers!
f
fast-garage-66093
10/14/2022, 10:03 PMWe just added the diagnostics feature in the 1.6.0 release, and it is mostly just plumbing so far; there are only a handful of checks so far. And we do have the functionality to add a link to the diagnostic, but it is currently empty because the corresponding doc landing page did not exist yet.
fast-garage-66093
10/14/2022, 10:03 PMBut I also think the message could provide mode information directly, as well as hints on how to fix it.
n
numerous-night-87848
10/14/2022, 10:04 PMI do have multiple kube contexts available, so now that I know that that’s what it’s talking about, it makes sense.
numerous-night-87848
10/14/2022, 10:05 PMThanks for your help!
f
fast-garage-66093
10/14/2022, 10:06 PMYou are welcome!
22 Views