Compare to kubespray

[varac]

I'm wondering why you choose to develop an own ansible role and not use kubespray ? COuld you pls document this/compare both in your README.md ?

[geerlingguy]

Kubespray does a heck of a lot more than what this role aims to achieve; basically this role is nice for building lightweight Kubernetes clusters using kubeadm and minimal dependencies.

I mostly use it for test clusters and for the Raspberry Pi Dramble.

But I will add some notes in the README about who should use this role, what its best use cases are, etc., that is a good idea for someone who might believe this role should be their be-all-and-end-all Kubernetes-related role (it should not :).

Also might do well to mention:

• https://github.com/geerlingguy/ansible-role-k8s_manifests
• https://github.com/geerlingguy/ansible-role-ecr_container_build

Which I also use with EKS clusters for many production apps/clusters.

[stale]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[geerlingguy]

Not stale.

[stale]

This issue is no longer marked for closure.

[trickert76]

After reading this issue, I had a deeper look into kubespray.

Yes, it makes much more then this role - but it uses for example simple binary downloads instead of concrete maintained distribution packages and also it is very confusing. For example you cannot simply apply the roles to your own environment/inventory. You need to use the project "as is".

So kubespray makes things different and there are environments where you aren't allowed to install none-packaged software. In that case this role is a good base for starting to configure Kubernetes.

Of course a quick note about that in the README would help others to understand, what is the difference and may help to find issues and customization with your own setup.

[TonyRouse]

but it uses for example simple binary downloads instead of concrete maintained distribution packages

I'll add, kubespray almost relies on resource download links that don't offer arm versions (auto builds URLs), and they 404 and fail on Raspberry Pi's.