Describe the bug
Connecting a cluster via kubeconfig upload repeatedly results in an "error" status card, reproduced with more than one different kubeconfig file (so it isn't specific to one broken kubeconfig).
Steps to reproduce
- Go to Clusters → + Connect cluster
- Upload a kubeconfig with a working context (verified reachable via
kubectl separately)
- Connect
- Entry shows status
error and stays there
Expected behavior
A valid, reachable kubeconfig context should connect successfully and show online.
Additional context
Tried with multiple different kubeconfig files, same result each time. Each failed attempt also left behind a new duplicate entry rather than retrying against an existing one, see the duplicate-entry issue. Needs server-side logs from a repro (journalctl/discovery logs around the failed connection attempt) to identify the actual failure cause, e.g. exec-auth plugin, network reachability from the host running infracanvas serve, TLS/cert handling, etc.
Describe the bug
Connecting a cluster via kubeconfig upload repeatedly results in an "error" status card, reproduced with more than one different kubeconfig file (so it isn't specific to one broken kubeconfig).
Steps to reproduce
kubectlseparately)errorand stays thereExpected behavior
A valid, reachable kubeconfig context should connect successfully and show
online.Additional context
Tried with multiple different kubeconfig files, same result each time. Each failed attempt also left behind a new duplicate entry rather than retrying against an existing one, see the duplicate-entry issue. Needs server-side logs from a repro (
journalctl/discovery logs around the failed connection attempt) to identify the actual failure cause, e.g. exec-auth plugin, network reachability from the host runninginfracanvas serve, TLS/cert handling, etc.