4 ms·

> There's no procedure for setting up a single host for development purposes or to have a Dokku-like personal PaaS." Can you clarify what you mean by this? Sin

by theptip 10y ago

> There's no procedure for setting up a single host for development purposes or to have a Dokku-like personal PaaS." Can you clarify what you mean by this? Since the beginning (pre-1.0) it's been possible to stand up a cluster on bare metal/VMs using a single command. This used to be done with the `kube-up.sh`[1] tool, which has been replaced with kubeadm in 1.6 [1]. If anything, I thought the fair complaint would be that there are too many ways to set up a cluster, and it's confusing to figure out which is the right one [2]. [1]: https://kubernetes.io/docs/getting-started-guides/kubeadm/ https://kubernetes.io/docs/getting-started-guides/kubeadm/ [2]: https://kubernetes.io/docs/setup/pick-right-solution/#table-of-solutions https://kubernetes.io/docs/setup/pick-right-solution/#table-...

Veratyr 10y ago
The problem with these tools for me was that they required either Ubuntu or CentOS/RHEL. I was installing on bare metal running Fedora and I'm unwilling to rebuild my machine for one application. I think I eventually got something set up using the manual documentation but at the time said documentation resulted in a completely insecure installation, entirely unauthenticated. Since I don't have (or want) a "private" network and the docs didn't tell me how to get security any other way, I just gave up on Kubernetes. And really, it's incredibly frustrating how inflexible the docs and setup tools are. As detailed in another comment (https://news.ycombinator.com/item?id=14296176 https://news.ycombinator.com/item?id=14296176), Kubernetes really just consists of Docker and 6 Go binaries. There's no reason setup should be so difficult and certainly no reason why it should be OS dependent.
- theptip 10y ago
  Got you, that's fair. It's definitely something that's been a pain point in the past, and is what kubeadm was designed to solve. There are actually a lot of tedious configuration parameters that need to be tuned per-distro, which is why there's only now a candidate for a unified solution; it's harder than you might think to create a truly generic tool for this job. (Take a look at the kube-up saltstack files if you want to be horrified by some surprising complexity). Nowadays, it looks like there are a couple options on Fedora, specifically https://kubernetes.io/docs/getting-started-guides/fedora/fedora_ansible_config/ https://kubernetes.io/docs/getting-started-guides/fedora/fed... https://kubernetes.io/docs/getting-started-guides/fedora/flannel_multi_node_cluster/ https://kubernetes.io/docs/getting-started-guides/fedora/fla... If you're looking for something that "Just Works (tm)", the ansible config (above) would be my bet for where to start these days.

by theptip 10y ago

Veratyr 10y ago

The problem with these tools for me was that they required either Ubuntu or CentOS/RHEL. I was installing on bare metal running Fedora and I'm unwilling to rebuild my machine for one application. I think I eventually got something set up using the manual documentation but at the time said documentation resulted in a completely insecure installation, entirely unauthenticated. Since I don't have (or want) a "private" network and the docs didn't tell me how to get security any other way, I just gave up on Kubernetes. And really, it's incredibly frustrating how inflexible the docs and setup tools are. As detailed in another comment (https://news.ycombinator.com/item?id=14296176 https://news.ycombinator.com/item?id=14296176), Kubernetes really just consists of Docker and 6 Go binaries. There's no reason setup should be so difficult and certainly no reason why it should be OS dependent.

theptip 10y ago
Got you, that's fair. It's definitely something that's been a pain point in the past, and is what kubeadm was designed to solve. There are actually a lot of tedious configuration parameters that need to be tuned per-distro, which is why there's only now a candidate for a unified solution; it's harder than you might think to create a truly generic tool for this job. (Take a look at the kube-up saltstack files if you want to be horrified by some surprising complexity). Nowadays, it looks like there are a couple options on Fedora, specifically https://kubernetes.io/docs/getting-started-guides/fedora/fedora_ansible_config/ https://kubernetes.io/docs/getting-started-guides/fedora/fed... https://kubernetes.io/docs/getting-started-guides/fedora/flannel_multi_node_cluster/ https://kubernetes.io/docs/getting-started-guides/fedora/fla... If you're looking for something that "Just Works (tm)", the ansible config (above) would be my bet for where to start these days.