The kubeconfig environment variable typically uses a colon-separated format for specifying multiple paths. However, the Kubernetes Go client library currently only supports a single path. This inconsistency can be confusing for developers. To simplify things, let's make the Go client accept the colon-separated format for kubeconfig paths, making it consistent with the standard environment variable format.
Following is the simple example to explain the issue:
Why is this needed?
Currently, users have to do extra work to get the config-path value from KUBECONFIG env. The Go client library expects a single value, but the system environment variables for KUBECONFIG are separated by colons. Let's make the Go client accept the KUBECONFIG env value readily. This would make it consistent with how the system handles these variables and make things easier for developers
What would you like to be added?
The kubeconfig environment variable typically uses a colon-separated format for specifying multiple paths. However, the Kubernetes Go client library currently only supports a single path. This inconsistency can be confusing for developers. To simplify things, let's make the Go client accept the colon-separated format for kubeconfig paths, making it consistent with the standard environment variable format.
KUBECONFIG env doc: https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable
Following is the simple example to explain the issue:
Why is this needed?
Currently, users have to do extra work to get the config-path value from
KUBECONFIG
env. The Go client library expects a single value, but the system environment variables forKUBECONFIG
are separated by colons. Let's make the Go client accept theKUBECONFIG
env value readily. This would make it consistent with how the system handles these variables and make things easier for developers