Problem with add and merge

[Evantage-WS]

Describe the bug
When merging 2 configs or adding a config, the name is not preserved

To Reproduce
I have a cluster
+------------+---------+------------+ .....
|..CURRENT...|....NAME...|...CLUSTER..| .....
+=========+=======+=========+ .....
| ....................|..test-vm..|...test-vm.....| .....

When adding a second config via kubecm add -f /tmp/config or kubecm merge "~/.kube/config" /tmp/config -y the name (context) of the first cluster is changed to config

+------------+---------+------------+ .....
|..CURRENT...|....NAME...|...CLUSTER..| .....
+=========+=======+=========+ .....
| ....................|...config...|...test-vm.....| .....
+------------+---------+------------+ .....
| ....................|..cluster2.|....cluster2....| .....

Expected behavior
It should not rename the cluster config name

Desktop (please complete the following information):

• OS: MacOS
• Version Ventura 13.0.1

Thanks!

[sunny0826]

In order to avoid cluster name conflicts, cluster names are renamed when adding and merging. I would also like to try to change this situation, please ask if there is a better suggestion for improvement to solve this problem.

[Evantage-WS]

Just check for duplicate names first or do a dry-run of the merge or merge it to a temp place first and check if the names are ok?

With the current renaming it is pretty hard to remove a config based on the clustername.

[sunny0826]

This issue will be fixed in the next version.

[soostdijck]

I love the concept of kubecm, but it wrecked my existing kube config in the first minute of trying it out when I used merge to add a kubeconfig to my existing config.
Shame this has been open for 9 months without a fix. I'll just restore a backup and go back to kubectx I suppose.

[sunny0826]

@soostdijck Very sorry for the bad experience. You can actually use the -cover and --config flags to generate kubeconfig in the specified directory instead of overwriting the source kubeconfig file.