5 ms·

One data point: I've wanted to but so far have not made much progress. I'd say my biggest impediment has been documentation: I can get it installed, but making

One data point: I've wanted to but so far have not made much progress. I'd say my biggest impediment has been documentation: I can get it installed, but making it work seems to be beyond the scope of the documentation. I got closest once I found out about "kubespray" to install the cluster rather than using the official Kubernetes installation docs process. I spent a couple weeks not quite full time going through tutorials, reading the documentation, reading blog posts and searching for solutions to the problems I was having. My biggest problem was with exposing the services "to the outside world". I got a cluster up quickly and could deploy example services to it, but unless I SSH port forwarded to the cluster members I couldn't access the services. I spent a lot of time trying to get various ingress configurations working but really couldn't find anything beyond an introductory level documentation to the various options. Kubespray and one blog post I stumbled across got me most of the way there, but at that point I had well run out of time for the proof of concept and had to get back to other work. My impression was that Kubernetes is targeted to the large enterprise where you're going to go all in with containers and can dedicate a month or two to coming up to speed. Many of the discussions I saw talked about or gave the impression of dozens of nodes and months of setup. Other options I'll probably look at when I have time to look at it again: Deis https://deis.com/ https://deis.com/ , Dokku http://dokku.viewdocs.io/dokku/ http://dokku.viewdocs.io/dokku/ , Flynn https://flynn.io/ https://flynn.io/ , LXC https://linuxcontainers.org/lxc/introduction/ https://linuxcontainers.org/lxc/introduction/ and (though I'd been trying to avoid it) Docker Swarm https://docs.docker.com/engine/swarm/ https://docs.docker.com/engine/swarm/

digaozao 9y ago
Take a look at rancher too. https://rancher.com/ https://rancher.com/ Rancher 2.0 promises nice UI for K8s
raesene9 9y ago
If you're looking for a better "out of the box" experience, I'd recommend having a look at OpenShift. You can use either their free tier in cloud or use the Open source OpenShift Origin for trials (there's also MiniShift, which is similar to MiniKube). From my looking at it OpenShift comes with some of the parts that base Kubernetes leaves to plugins, so things like ingress, networking etc are installed as part of the base.
egeozcan 9y ago
Dokku is great if you want to deploy on a single machine. I've been happy with it so far and haven't been lucky enough to have a problem of scaling yet.
andrewstuart2 9y ago
Are you trying to play around, or set up a working cluster? If you just want to play around, I'd suggest just using minikube to get things going. Anecdotally, I got an HA cluster running across 3 boxes in the space of about a month, with maybe 2-3 hours a day spent on it. The key for me was iterating, and probably that I have good experience with infrastructure in general. I started out with a single, insecure machine, added workers, then upgraded the workers to masters in an HA configuration. I don't think it is really that hard to get a cluster going if you have some infrastructure and networking experience, especially if you start with low expectations and just tackle one thing at a time incrementally.
- oso2k 9y ago
  Full Disclosure: I work for Red Hat in the Container and PaaS Practice in Consulting. At Red Hat, we define an HA OpenShift/Kubernetes cluster as 3x3xN (3 masters, 3 infra nodes, 3 or more app nodes) [0] which means the API, etcd, the hosted local Container Registry, the Routers, and the App Nodes all provide (N-1)/2 fault tolerance. Not to brag, since we're well practiced at this, but I can get a 3x3x3 cluster in a few hours, I've lead customer to a basic 3x3x3 install (no hands on keyboard) in less than 2 days, and our consultants are able to install a cluster in 3-5 working days about 90% of the time, even with impediments like corporate proxies, wonky DNS or AD/LDAP, not so Enterprise Load Balancers, and disconnected installs. Making a cluster read for production is about right-sizing and doing good testing. [0] http://v1.uncontained.io/playbooks/installation/#cluster-design-architecture http://v1.uncontained.io/playbooks/installation/#cluster-des...
  - merb 9y ago
    would be good if the "Enterprise Load Balancer" would just be another set of servers (with HAProxy + keepalived or something else, I love the "single ip" failover) Edit: especially load balacing the master servers. (that's actually the hard part of k8s, not even setting it up with/out openshift/ansible whatever) load balancing services on k8s itself is basically just running either calico network and use one or two haproxy deployments of size 1 with a ip annotation or just using https://github.com/kubernetes/contrib/tree/master/keepalived-vip https://github.com/kubernetes/contrib/tree/master/keepalived...
piaste 9y ago
Docker Swarm might be worth looking at regardless: (1) it's like 15 minutes to learn how it works and then maybe a morning or so playing around with it. Very low investment. (2) if you're already using docker-compose, it's pretty much an in-place switch. You might need to deal with a few restrictions (mandatory overlay network, no custom container names, no parameterized docker-compose), in exchange you'll get zero-downtime upgrades, automated rollbacks, and of course the ability to add more machines to your swarm.
oblio 9y ago
Rancher 2.0 with Kubernetes. Should make things a lot easier.

digaozao 9y ago

Take a look at rancher too. https://rancher.com/ https://rancher.com/ Rancher 2.0 promises nice UI for K8s

raesene9 9y ago

If you're looking for a better "out of the box" experience, I'd recommend having a look at OpenShift. You can use either their free tier in cloud or use the Open source OpenShift Origin for trials (there's also MiniShift, which is similar to MiniKube). From my looking at it OpenShift comes with some of the parts that base Kubernetes leaves to plugins, so things like ingress, networking etc are installed as part of the base.

egeozcan 9y ago

Dokku is great if you want to deploy on a single machine. I've been happy with it so far and haven't been lucky enough to have a problem of scaling yet.

andrewstuart2 9y ago

Are you trying to play around, or set up a working cluster? If you just want to play around, I'd suggest just using minikube to get things going. Anecdotally, I got an HA cluster running across 3 boxes in the space of about a month, with maybe 2-3 hours a day spent on it. The key for me was iterating, and probably that I have good experience with infrastructure in general. I started out with a single, insecure machine, added workers, then upgraded the workers to masters in an HA configuration. I don't think it is really that hard to get a cluster going if you have some infrastructure and networking experience, especially if you start with low expectations and just tackle one thing at a time incrementally.

oso2k 9y ago
Full Disclosure: I work for Red Hat in the Container and PaaS Practice in Consulting. At Red Hat, we define an HA OpenShift/Kubernetes cluster as 3x3xN (3 masters, 3 infra nodes, 3 or more app nodes) [0] which means the API, etcd, the hosted local Container Registry, the Routers, and the App Nodes all provide (N-1)/2 fault tolerance. Not to brag, since we're well practiced at this, but I can get a 3x3x3 cluster in a few hours, I've lead customer to a basic 3x3x3 install (no hands on keyboard) in less than 2 days, and our consultants are able to install a cluster in 3-5 working days about 90% of the time, even with impediments like corporate proxies, wonky DNS or AD/LDAP, not so Enterprise Load Balancers, and disconnected installs. Making a cluster read for production is about right-sizing and doing good testing. [0] http://v1.uncontained.io/playbooks/installation/#cluster-design-architecture http://v1.uncontained.io/playbooks/installation/#cluster-des...
- merb 9y ago
  would be good if the "Enterprise Load Balancer" would just be another set of servers (with HAProxy + keepalived or something else, I love the "single ip" failover) Edit: especially load balacing the master servers. (that's actually the hard part of k8s, not even setting it up with/out openshift/ansible whatever) load balancing services on k8s itself is basically just running either calico network and use one or two haproxy deployments of size 1 with a ip annotation or just using https://github.com/kubernetes/contrib/tree/master/keepalived-vip https://github.com/kubernetes/contrib/tree/master/keepalived...

piaste 9y ago

Docker Swarm might be worth looking at regardless: (1) it's like 15 minutes to learn how it works and then maybe a morning or so playing around with it. Very low investment. (2) if you're already using docker-compose, it's pretty much an in-place switch. You might need to deal with a few restrictions (mandatory overlay network, no custom container names, no parameterized docker-compose), in exchange you'll get zero-downtime upgrades, automated rollbacks, and of course the ability to add more machines to your swarm.

oblio 9y ago

Rancher 2.0 with Kubernetes. Should make things a lot easier.