I was a total noob at this, and started setting up a kube cluster on 10th of May, and I managed to set up a working cluster by the middle of the week. It’s actually not as complicated as expected.
I still agree with you, because no one should take setting up and running kube lightly – it’s actually a lot of work.
And there’s a few guides for setting it up automatically in vagrant, or on aws, or on Juju-managed clouds.
Sadly, Kube is very barebones – only doing scheduling, if you add a storage provider such as portworx (only block storage) or rook (block and object storage) you also gain that, but it doesn’t do any user auth functionality.
That’s something I’m atm still searching for, something allowing me to easily register and remove users, add them to groups and do RBAC, but without using ldap as backend, and with a way to get it working with OpenID Connect and OAuth 2.0, as well as with Shibboleth, Kerberos, and an LDAP compatibility layer (but with app-specific passwords there).
Comments
I was a total noob at this, and started setting up a kube cluster on 10th of May, and I managed to set up a working cluster by the middle of the week. It’s actually not as complicated as expected.
I still agree with you, because no one should take setting up and running kube lightly – it’s actually a lot of work.
This is good, it means kube is about 100x easier to set up than openstack.
On the other hand, Google will run your Kube for free up to 5 nodes.
There’s actually even a hobbyists guide for running kube yourself: https://github.com/hobby-kube/guide
And there’s a few guides for setting it up automatically in vagrant, or on aws, or on Juju-managed clouds.
Sadly, Kube is very barebones – only doing scheduling, if you add a storage provider such as portworx (only block storage) or rook (block and object storage) you also gain that, but it doesn’t do any user auth functionality.
That’s something I’m atm still searching for, something allowing me to easily register and remove users, add them to groups and do RBAC, but without using ldap as backend, and with a way to get it working with OpenID Connect and OAuth 2.0, as well as with Shibboleth, Kerberos, and an LDAP compatibility layer (but with app-specific passwords there).