Is kubespray-cli deprecated?

[kasunbg]

Hi kubespray devs,

I have noticed that kubespray-cli has been deprecated by kubespray parent project as seen in here: kubernetes-sigs/kubespray@1869aa3#diff-a39c9f7aa728d5fa3b973bc6ba49228a

Kubespray guide mentions that cli is not actively maintained, but I see several commits over the last few months.

This is a red flag for the adoption of this wonderful tool. Could you please provide you opinion on this?

[oz123]

I spent the last two days trying to use this project on OpenStack.
This projects seems under-documented and dead.
It will crash and throw errors on newer ansible versions and on Ubuntu 16.04 .

[oz123]

So, just because of the potential of this tool, I spent some time fixing the errors I encountered into.
Patches are found in the fork here https://github.com/noris-network/kubespray-cli

[ssbarnea]

An answer here would be appreciated. The question is quite useful.

[oz123]

@ssbarnea what's your use case? I actually stopped using ansible so with it I stopped using kube-spray at all. But I am just wondering ...

[ssbarnea]

I asked because I recently started to use kubespray to deploy and maintain a homelab cluster. Experience so far was good with only few glitches. This morning I found about the cli tool but but discovered that is maked in documentarion as not maintained. For this reason I wanted to know if this is “official” and we can even see the repo marked as archived.

BTW, what are you using now? I am curious in case my experience with kubespray goes south.

[oz123]

@ssbarnea I use a collection of bash scripts with kubeadm.
I never liked ansible, it is just used my work place. Ansible is really a terrible piece of software. So I am not surprised your experience isn't nice.
Just use kubeadm (I know kubespray started using it too, but there is no real need to wrap kubeadm with ansible, also you can write your own playbook using kubeadm in less then 1 hour)