helm/helm

TestUserAgentHeaderInK8sRESTClientConfig appears to fail when you have a bad .kube/config

Open

#31470 opened on Nov 9, 2025

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Go (29,815 stars) (7,602 forks)batch import
bughelp wanted

Description

TestUserAgentHeaderInK8sRESTClientConfig appears to fail when you have a bad .kube/config

In my case, current context was no longer a valid cluster.

Ideally the unit tests wouldn't rely on the current k8s environment.

Contributor guide

Tech stack
gorest api
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go testingkubeconfig formatHelm project setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Examine the test function TestUserAgentHeaderInK8sRESTClientConfig in the Helm codebase. Currently it relies on the user's default kubeconfig (~/.kube/config). To fix, refactor the test to use a temporary or mock kubeconfig file, for example by setting the KUBECONFIG environment variable to a test specific config. Ensure no external cluster state is required.