A Golang related question. The "kubectx" tool, I see it

Question

A Golang related question. The "kubectx" tool, I see it

its doing a lot more (party because of kubens utility). Heres the github repo https://github.com/ahmetb/kubectx

I am thinking, for kubectx (changing the context), shouldnt it be as simple as reading the kube config file to list all the clusters. To change the context, update the yaml value of (current-context)?

I am trying to understand why is it so heavy (ignore the kubens part. I understand it needs to talk to the api server to list the namespaces etc)

0

27.06.2022

2 ответов

20 просмотров

Nish S Автор вопроса

Raj T
It’s just a wrapper , what is so heavy about it ?

I mean why is it going through all that long code for changing the context when it could be as simple as 1. reading in the kubeconfig and get a list of clusters 2. Change the “current-context” value if someone wants to

0

29.06.2022

Raj T · Accepted Answer

Raj T

It’s just a wrapper , what is so heavy about it ?

0

29.06.2022

Похожие чаты

A Golang related question. The "kubectx" tool, I see it

2 ответов

Похожие вопросы