openebs-archive/openebsctl

environment KUBECONFIG not working windows

Open

#156 opened on Jun 24, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (22 forks)auto 404
good first issue

Repository metrics

Stars
 (33 stars)
PR merge metrics
 (PR metrics pending)

Description

setting environment KUBECONFIG seems to add random folder to file name on windows 11?

PS C:\Users\sas_2\Documents\Developer\talos> $env:KUBECONFIG=".\mycluster\kubeconfig"
PS C:\Users\sas_2\Documents\Developer\talos> kubectl openebs version 
2023/06/24 23:23:46 error creating kubernetes client: failed to build Kubernetes clientset: Could not build config from flags: CreateFile mycluster\kubeconfig\.kube\config: The system cannot find the path specified.
Error: exit status 1

PS C:\Users\sas_2\Documents\Developer\talos> kubectl openebs version --kubeconfig ".\mycluster\kubeconfig"
COMPONENT             VERSION
Client                v0.5.0
OpenEBS CStor         3.4.0
OpenEBS Jiva          3.4.0
OpenEBS LVM LocalPV   Not Installed
OpenEBS ZFS LocalPV   Not Installed

EDIT: even if i hard code the kubeconfig file its the same problem

$env:KUBECONFIG="C:\Users\sas_2\Documents\Developer\talos\mycluster\kubeconfig"
PS C:\Users\sas_2\Documents\Developer\talos> kubectl openebs get volumes --cas-type=cstor
2023/07/16 17:10:29 error creating kubernetes client: failed to build Kubernetes clientset: Could not build config from flags: CreateFile C:\Users\sas_2\Documents\Developer\talos\mycluster\kubeconfig\.kube\config: The system cannot find the path specified.
Error: exit status 1

Contributor guide

Research direction
Investigate how openebsctl reads the KUBECONFIG environment variable and constructs the path. The error shows that it appends `\.kube\config` to the given path. Look at the client go library's `clientcmd.BuildConfigFromFlags` and any custom path handling in the codebase that might be incorrectly joining paths on Windows. Check for usage of `filepath.Join` vs path concatenation and ensure compatibility with Windows paths.
Tech stack
go
Domain
clibackend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GokubectlWindows environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70