straight-vr-2696
03/07/2023, 3:22 PMrapid-eye-50641
03/07/2023, 5:32 PMstraight-vr-2696
03/08/2023, 7:47 AMjolly-forest-99711
03/08/2023, 6:18 PMkubectl
merges multiple kubeconfig files into one config when it runs. Did you replace the old one? While I'm not too familiar with this part of Rancher Desktop, I can see that causing problems.
Have you tried setting the KUBECONFIG
environment variable to multiple files (by separating the paths with a :
)? That is something that should work - if it doesn't it may be a bugstraight-vr-2696
03/09/2023, 7:27 AMKUBECONFIG
env variable to point to that specific kubeconfig. Is it possible that Rancher Desktop looks at this environment variable when trying to open the dashboard?
I think this still wouldn't explain why, if I delete my remote kubeconfig or put the config inside the config file, everything starts to work againKUBECONFIG
env variable is actually set to point both to the config and my custom kubeconfig, but they are separated by ;
(I'm on Windows 11). I assume that this is correct though, because i was able to use kubectl config use-context
and switch between the two contexts with no problemjolly-forest-99711
03/09/2023, 4:53 PMKUBECONFIG
environment variable? Does it modify it globally? If so, I could see it causing problems for dashboard...rancher-desktop
kubeconfig context, so the problem can't be due to dashboard using the wrong context. Assuming KUBECONFIG
is set globally, the dashboard should still be finding the old rancher-desktop
context...straight-vr-2696
03/10/2023, 7:55 AMKUBECONFIG
variable is set globally. I will open an issue with the steps that brought me there. I also have forgot to mention that, loooking at the dashboard logs, I see
Proxy Error: Error: connect ECONNREFUSED 127.0.0.1:9443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) {
errno: -4078,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 9443
}
2023-03-10T07:51:49.604Z: [HPM] Error occurred while proxying request 127.0.0.1:6120/api/v1/namespaces/cattle-ui-plugin-system/services/<http:ui-plugin-operator:80/proxy/index.json> to <https://127.0.0.1:9443/> [ECONNREFUSED] (<https://nodejs.org/api/errors.html#errors_common_system_errors>)
I am behind a corporate proxy, so I don't know if it can affect the dashboard in any way (but i guess it shouldn't because it should be working with local stuff, right?). Thank you for the help, I'll open an issue and be as detailed as possiblejolly-forest-99711
03/10/2023, 5:02 PM