Skip to content

Crash when opening settings panel after a first fresh install #1782

Closed

Description

@TristofCuber

Describe the bug

I installed Radar Desktop on Windows for the first time using scoop (using a regular console, not an admin). Then I open the UI, click on settings and it crashes.

To reproduce

Open Radar Desktop and click on settings. I tried rebooting my machine, without any difference. I also tried copying the folder %USERPROFILE%/.kube containing setup config from a colleague that does not have the issue but still, no difference and the Kubernetes machines are not yet seen in the tool

Expected behavior

Diagnostics

Diagnostics snapshot

Radar Diagnostics

Version: 1.13.1 | Go: go1.26.8 | OS: windows/amd64 | Uptime: 19s

Connection

  • State: disconnected
  • Context: ``
  • Error: Kubeconfig initialization failed; see local Radar logs for details
  • Error Type: config

Kubeconfig

  • Mode: single | Files: 1 | Contexts (after source resolution): 0
  • KUBECONFIG Captured From Shell: No | Ignored: No
  • Current Context Uses Exec: No

Cluster

  • Platform: unknown | K8s: `` | Nodes: 0 | Namespaces: 0

Event Pipeline

  • Received: 0 | Dropped: 0 | Uptime: 0s

Informers

  • Typed: 0 | Dynamic: 0

Prometheus

  • Connected: No

Performance

  • Topology Builds: 0
  • SSE: 0 broadcasts, 0 drops

Runtime

  • Heap: 15.2 MB | Objects: 57.0K | Goroutines: 20 | CPUs: 20
  • SSE Clients: 1

Config

  • Port: 0 | Dev: false | Timeline: memory | History: 10000 | MCP: true | Prometheus URL: auto

Recent Errors (2)

  • [k8s-init] failed to build kubeconfig client config (mode=single, files=0): empty kubeconfig (no configuration provided) (8:42:57 AM)
  • [env-enrich] KUBECONFIG not found in login shell (unknown -l -i); multi-file configs from .zshrc/.bashrc will not be visible (8:42:57 AM)
con

Activity

  1. nadaverell commented on Sep 16, 2026

    @nadaverell
    Contributor

    Thanks for the report, and for including the diagnostics. Reproduced: when Radar Desktop starts without a usable kubeconfig, opening Settings hit a nil-pointer crash in the Prometheus auto-discovery path on the Go side, so it's nothing about your machine or the scoop install. Fix is in #1787 and will be in v1.14, which is going out in the next few minutes.

    On the copied kubeconfig: the diagnostics still show zero contexts loaded, so Radar isn't finding it. On Windows it reads %USERPROFILE%\.kube\config (the file, not just the folder) unless KUBECONFIG is set. Once v1.14 is installed, the Connection section in Settings will also let you point it at a file directly.

  2. TristofCuber commented on Sep 16, 2026

    @TristofCuber
    Author

    Great, I'm impressed with the speed at which this was solved. Thanks a lot!

  3. added a commit that references this issue on Sep 16, 2026
    0da1de7
  4. nadaverell commented on Sep 16, 2026

    @nadaverell
    Contributor

    We try :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions