Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
1–10 of 25 posts
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#2As someone who doesn't know enough about K8s, this looks like an amazingly easy way to get stuck in.
Can anyone who has experience with real deployments advise on what pain-points may be encountered by growing something like this further than N nodes (and talk about what N might be?)
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#3As someone who doesn't know enough about K8s, this looks like an amazingly easy way to get stuck in. Can anyone who has experience with real deployments advise on what pain-points may be encountered by growing something like this further than N nodes (and talk about what N might be?)
If you want to get started with Kubernetes I'd recommend either, Kelsey Hightower's Kubernetes the hard way (https://github.com/kelseyhightower/kubernetes-the-hard-way) which is a good way to start getting an understanding of the various components and how they fit together or, if you want to try out running workloads on a cluster, Kubeadm (https://kubernetes.io/docs/setup/independent/create-cluster-...)
If you're interested in books on the topic, I like Kubernetes in Action (https://www.manning.com/books/kubernetes-in-action) or Kubernetes: Up and running (http://shop.oreilly.com/product/0636920043874.do)
One of the challenges with Kubernetes is that it's pretty fast moving, so it's a good idea to work with resources that are up to date. I know a last commit from May doesn't seem very old but that's going to a least be missing 1.7 and could be missing 1.6 or earlier as well.
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#4This sounds like buzzword bingo.
I can't tell without reading the source, is this any different from minikube? I see a mention of NUCs and netboot in the README, so I'm guessing it's slightly more, but not documented.
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#5As someone who doesn't know enough about K8s, this looks like an amazingly easy way to get stuck in. Can anyone who has experience with real deployments advise on what pain-points may be encountered by growing something like this further than N nodes (and talk about what N might be?)
I've found a few not-so-obvious pain points on my very limited k8s experience.
1) k8s makes a lot of sense for stateless applications (such as your website) but not so much for stateful applications that require a client to connect to the same container every time (there are ways to do it, but they are a pain in the ass.)
2) Tooling is getting better with time, but it's still pretty green. Packages for your usual orchestration tools like Puppet and Ansible are volunteer work so they get easily out of sync, or require more work than you'd expect to get going. Using their suggested YAML format leads to another problem: there's no easy way to keep secrets outside of the configuration files, unless you build your own process around it
3) Some pieces, like a replicated DB, might be easier to be kept outside of the k8s cluster. You can technically run them there, but they weren't designed for running in that kind of environment and sometimes it shows
4) The CI/CD story using Jenkins pipelines is far from solved. There are several packages that provide some solutions, but the documentation tends to be horrible and that leads to days of debugging through trial and error
5) Leaky abstractions everywhere. As an example, the Jenkins plugins to build using your k8s cluster suggests using the "credentials" system, but you need to add them manually after you boot the Jenkins service. Then your slaves stop receiving the credentials and you have to reboot Jenkins (I had to reboot it on average every 3 or 4 builds.)
Don't let that discourage you from using k8s as a "run" cluster, if your app is a shared-nothing, stateless app. It's so much easier to setup (specially on Azure and GCP) and it obviates the need for setting up Puppet + Sensu + load balancing just to make sure your service keeps running when a node dies.
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#6As someone who doesn't know enough about K8s, this looks like an amazingly easy way to get stuck in. Can anyone who has experience with real deployments advise on what pain-points may be encountered by growing something like this further than N nodes (and talk about what N might be?)
If you want to get started with Kubernetes I'd recommend either, Kelsey Hightower's Kubernetes the hard way ( https://github.com/kelseyhightower/kubernetes-the-hard-way ) which is a good way to start getting an understanding of the various components and how they fit together or, if you want to try out running workloads on a cluster, Kubeadm ( https://kubernetes.io/docs/setup/independent/create-cluster-... ) If you'r…
Just to parrot... the governance and development model for Kubernetes is amazing. There are releases every three months and it is like clockwork. That said I usually wait for the first point release to ship before upgrading. 1.x.0 releases always feel like an RC and there's usually some critical bug fixed between 1.x.0 and 1.x.1.
Project plug. I am building a free service and tool for instantaneous cloud-running ephemeral Kubernetes clusters called Kubernaut. If you just want to play around with Kubernetes and start learning it is a great tool. Also useful for CI use via Travis: https://github.com/datawire/kubernaut
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#7kubernetes has so much momentum and developer interest. I rarely see anything about DC/OS which is what they choose at my work last month, apparently its DC/OS is more 'battle tested' in enterprise.
I don't think i even want to setup dc/os on my laptop and play with it, seems almost impossible to run mesos on osx . All these articles are making me resent DC/OS :D.
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#8As someone who doesn't know enough about K8s, this looks like an amazingly easy way to get stuck in. Can anyone who has experience with real deployments advise on what pain-points may be encountered by growing something like this further than N nodes (and talk about what N might be?)
I've found a few not-so-obvious pain points on my very limited k8s experience. 1) k8s makes a lot of sense for stateless applications (such as your website) but not so much for stateful applications that require a client to connect to the same container every time (there are ways to do it, but they are a pain in the ass.) 2) Tooling is getting better with time, but it's still pretty green. Packages for your usual orc…
1)
That's true, but why not support shared state on shared storage. If that's not an option.
2) What exactly do you not like tooling wise.
3) Totally agree. I am actually working on replacing etcd with postgresql though.
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#9Earlier quoted context omitted.
I've found a few not-so-obvious pain points on my very limited k8s experience. 1) k8s makes a lot of sense for stateless applications (such as your website) but not so much for stateful applications that require a client to connect to the same container every time (there are ways to do it, but they are a pain in the ass.) 2) Tooling is getting better with time, but it's still pretty green. Packages for your usual orc…
1) That's true, but why not support shared state on shared storage. If that's not an option. 2) What exactly do you not like tooling wise. 3) Totally agree. I am actually working on replacing etcd with postgresql though.
Could you share more about #3 ?
How do you view that in regard to this discussion? https://github.com/kubernetes/kubernetes/issues/1957
Re: Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
#10kubernetes has so much momentum and developer interest. I rarely see anything about DC/OS which is what they choose at my work last month, apparently its DC/OS is more 'battle tested' in enterprise. I don't think i even want to setup dc/os on my laptop and play with it, seems almost impossible to run mesos on osx . All these articles are making me resent DC/OS :D.
DC/OS was developed with objectives that are not overlapping with K8s'.
Namely, they target machine management. While K8s is about container centric job management. Seems subtle, but if you think along these 2 lines, design decisions in 2 systems fall through naturally.