3 people 66e9107688 Fix(cli): guard vela top against nil rest.Config panic (#7279) ...

K8SVersion, velaCorePodUsage, and velaCLusterGatewayPodUsage in
references/cli/top/model/info.go called kubernetes.NewForConfig /
metrics.NewForConfig without checking for a nil *rest.Config first.
client-go panics with a nil-pointer dereference in that case instead
of returning an error, so vela top crashes instead of showing
Unknown/N/A for those fields.

Confirmed via two independent call paths that both panicked before
this fix: InfoBoard.Init (references/cli/top/component) and
App.Init (references/cli/top/view).

Added regression tests for all three functions with a nil config.

Signed-off-by: sakirr05 <sakirahmed75531@gmail.com>
Co-authored-by: sakirr05 <sakirahmed75531@gmail.com>

2026-08-12 11:25:16 +01:00

..

component

Chore: (deps): Update k8s to 1.29 (#6654)

2025-01-03 07:54:42 +08:00

config

fix: update YAML import path to use go.yaml.in/yaml/v3 and adjust dependencies in go.mod and go.sum (#6944)

2025-11-06 10:37:19 +00:00

model

Fix(cli): guard vela top against nil rest.Config panic (#7279)

2026-08-12 11:25:16 +01:00

utils

Feat(testing): Enhance Unit Test Coverage for Core Utility Packages (#6929)

2025-10-31 13:50:30 +00:00

view

Chore: update helm repo path in tests (#6797)

2025-06-13 07:13:25 -07:00