Kubernetes Config Handling

[ramanaleon]

Guys,

Quick Question Please:-

We have installed kubectl on one of the LINUX host and there are many users who use this host to trigger the KUBE commands. Catch here is all these calls from the users are handled by one generic account called "kube4u" and its home path is /app/kube4u.

So everytime when there is kubectl login the config file gets created under /app/kube4u/.kube/config path and this gets overwritten by the last recent user login. Which means a user who has logged in earlier and is in between the transaction gets impacted due to most recent user login as the token and username changes in the config file.

Solution I wish:

There should be individual space assigned for each of the userlogin and all the subsequent kubectl commands should refer that config path so that there wouldn't be any conflict between parallel user actions/logins.

I know something about --kubeconfig which allows us to show the config file. Could someone please assist here.

Regards, Ram

[ilackarms]

@ramanaleon hey, this repository is archived / no longer where we develop glooctl. check out https://github.com/solo-io/gloo, specifically the cli code can be found in https://github.com/solo-io/gloo/tree/master/projects/gloo/cli