Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker for Mac with Kubernetes

docs.docker.com

Post reply on HN
Print view View original

141–150 of 169 posts

Re: Docker for Mac with Kubernetes

#141

Post by dankohn1 »

csmiller wrote: post #88
linkmotif wrote: post #55

So confused by all the posts from people who say they run Swarm because kubernetes is too complicated or is only for huge deployments. I’ve had all sort of difficulties installing Docker. By hand it’s not trivial to get a secure install. Docker machine is great except it’s often broken. The Docker machine dev team is a tired, understaffed bunch that’s always playing a sisyphean whack-a-mole against dozens of cloud pr…

Have any recommended resources for learning Kubernetes? I've looked at it a few times, but it always seemed rather intimidating.

If you like videos, I recommend the free EdX course. If you don't I recommend the Katacoda interactive sessions.

https://kubernetes.io/docs/tutorials/

(Disclosure: I run CNCF, which hosts Kubernetes and funded the EdX course.)

Re: Docker for Mac with Kubernetes

#142

Post by kuschku »

pacala wrote: post #133
kuschku wrote: post #107

Earlier quoted context omitted.

> You either run Cloud + Kubernetes and get rolling in 15 minutes, or you hire IT headcount. You can always rent dedicated hardware – much cheaper than renting similar amounts of virtual servers, and the same administration and operations costs. It’s often even significantly cheaper than what GCE offers – but of course, setting up Kubernetes is more complicated.

Exactly. Hardware rental is one way to tackle provisioning. You're still left with all the other tasks required to bootstrap your own datacenter. As you build up the roll-your-own solution, you end up in the same place: hire IT headcount. If you are a small startup looking to validate market fit, your best bet is Cloud + Kubernetes. If you are an established business with millions of daily customers and serious IT he…

> Exactly. Hardware rental is one way to tackle provisioning. You're still left with all the other tasks required to bootstrap your own datacenter. As you build up the roll-your-own solution, you end up in the same place: hire IT headcount.

For a startup, building a datacenter isn’t required in the beginning.

I meant, literally renting existing hardware, in an existing datacenter. This is just a single step from renting VMs at AWS or GCE, but already improves costs significantly.

Re: Docker for Mac with Kubernetes

#143

Post by ownagefool »

pacala wrote: post #101
drdaeman wrote: post #77

Earlier quoted context omitted.

> Kubernetes on the other hand is trivial with GKE How do I install GKE on my servers? ;) > By hand it’s not trivial to get a secure install. The default install (basically, adding a repo and apt-get install docker-ce on Debian and derivatives - trivial to automate with Ansible) is reasonably secure if you view Docker as a tool for packaging and task scheduling with some nice extras and don't buy the marketed isolati…

> How do I install GKE on my servers? ;) Great question! All major Cloud providers offer managed Kubernetes services: https://cloud.google.com/kubernetes-engine https://azure.microsoft.com/en-us/services/container-service https://aws.amazon.com/eks https://www.ibm.com/cloud/container-service The choice is Cloud + Kubernetes vs. roll everything on your own hardware. Running your own hardware is a major IT effort. Kube…

https://kubernetes.io/docs/setup/independent/create-cluster-...

Re: Docker for Mac with Kubernetes

#144

Post by atombender »

Exuma wrote: post #128

One of my engineering friends told me he didn't use Kubernetes in the past because there was a single point of failure with it for distributed setups. I really wish I could remember what SPOF was pertaining to, but I just can't remember. Does anyone have any idea if this is still relevant/accurate information? He told me this maybe 2-3 years ago, so I was wondering how things have changed since then, or if anyone kno…

Kubernetes supports HA masters now: https://kubernetes.io/docs/admin/high-availability

Note that even if you don't have HA, Kubernetes being a SPOF isn't necessarily critical. Barring some kind of catastropic, cascading fault that affects multiple nodes and requires rescheduling pods to new nodes, a master going down doesn't actually affect what's currently running. Autoscaling and cronjobs won't work, clients using the API will fail, and failed pods won't be replicated, but if the cluster is otherwise fine, pods will just continue running as before. Ny analogy, it's a bit like turning off the engines during spaceflight. You will continue to coast at the same speed, but you can't change course.

Re: Docker for Mac with Kubernetes

#145

Post by StavrosK »

sandGorgon wrote: post #140
StavrosK wrote: post #74

Earlier quoted context omitted.

Thanks for the shoutout. Would you happen to have a writeup on how to do that, or a few lines on whether it's Swarm-aware somehow? I guess it can't be too hard to figure out, but if there's something that will speed that up, that's better.

No - you don't need it to be swarm aware at all. All you need to do is create a docker service out if traefik/nginx/haproxy/whatever and bind the ports of the service to type "ingress". From then on, all traffic is internal - and you deal with it normally from one docker service to another.

Ah, okay, so pretty agnostic. Sounds like this is geared towards single project deployments, though (ie it wouldn't be suited in a multitenant scenario), but that's good to know.

I've been looking for a Dokku replacement for running my side-projects on with easy scalability (by provisioning another server), but I haven't found anything that's suitable for running multiple apps together in a heroku-like way but still able to scale beyond a single server. Do you know of anything like that?

Re: Docker for Mac with Kubernetes

#146

Post by Exuma »

atombender wrote: post #144
Exuma wrote: post #128

One of my engineering friends told me he didn't use Kubernetes in the past because there was a single point of failure with it for distributed setups. I really wish I could remember what SPOF was pertaining to, but I just can't remember. Does anyone have any idea if this is still relevant/accurate information? He told me this maybe 2-3 years ago, so I was wondering how things have changed since then, or if anyone kno…

Kubernetes supports HA masters now: https://kubernetes.io/docs/admin/high-availability Note that even if you don't have HA, Kubernetes being a SPOF isn't necessarily critical . Barring some kind of catastropic, cascading fault that affects multiple nodes and requires rescheduling pods to new nodes, a master going down doesn't actually affect what's currently running. Autoscaling and cronjobs won't work, clients using…

Interesting, well thats great to know. Thanks for the ELI5 explanation.

Re: Docker for Mac with Kubernetes

#147

Post by amazingman »

driton wrote: post #82
alexellisuk wrote: post #38

I normally used minikube for openfaas development - I appreciate the efforts of the project, it's an invalueable tool. The DfM integration works very well for local development and I've got some screenshots below: https://twitter.com/alexellisuk/status/949595379326210048 Make sure you do a context-switch for kubectl too. I see some people talking about Swarm vs Kubernetes. Swarm has always maintained a less modular a…

Have you ever tried docker-compose? While the two solutions are obviously with different goals in mind, one being to fully run the kubernetes setup locally, and the other one to run a few docker containers who talk to one another, if it's for the purpose of running a simple-ish dev environment, in my experience, docker-compose is much faster and simpler than minikube.

docker-compose trades a better initial UX for far less flexibility and, funnily enough, higher practical complexity in the long run. It's great if you want to get from zero to MVP with as little thinking about what your infrastructure needs will be as possible. It's pretty awful, however, when you want to truly productionalize what you've done and you find out that in order to do so you'll have to use the newest Compose format, and your docker-compose.yml (and possibly additional supporting Compose) files are not at all easier to read or simpler to write than e.g. k8s objects in YAML.

Re: Docker for Mac with Kubernetes

#148

Post by amazingman »

xorcist wrote: post #32
sz4kerto wrote: post #13

Earlier quoted context omitted.

No, it didn't. Yes, k8s has 'won' in large-scale deployments, but if you're working at a small shop, then just imitating what Google does with millions of servers is dumb. Do what works at your scale -- and Swarm is extremely easy to manage. Many people ask why would someone use an orchestrator on a small cluster (dozens of hosts). Why not? Swarm is very easy to manage and maintain, using Puppet or Ansible is not les…

> Swarm is very easy to manage and maintain, using Puppet or Ansible is not less complicated The idea that dockerized software somehow is less dependent on configuration management seems to be a popular and completely misguided one. The two trends are completely separate, but I would argue from experience that unless you have absolutely nailed the configuration and integration of all your moving parts, don't even loo…

If you design your infrastructure and choose your tooling well, then containerized (not "dockerized") software is far less dependent upon configuration management; indeed, using Chef/Puppet/etc can be completely unnecessary for the containerized workload. To be clear, however, there is absolutely still a need for the now-traditional configuration management layer at the level of the hosts running your containerized workloads. What's kind of exciting about this is that the giant spaghetti madness that our configuration management repo has become—and I'm pretty sure it's not just us ;-)— at our org is going to be reduced in complexity and LOC by probably an order of magnitude as we transition to Kubernetes-based infrastructure.

Re: Docker for Mac with Kubernetes

#149

Post by amazingman »

bradmwalker wrote: post #56
sz4kerto wrote: post #13

Earlier quoted context omitted.

No, it didn't. Yes, k8s has 'won' in large-scale deployments, but if you're working at a small shop, then just imitating what Google does with millions of servers is dumb. Do what works at your scale -- and Swarm is extremely easy to manage. Many people ask why would someone use an orchestrator on a small cluster (dozens of hosts). Why not? Swarm is very easy to manage and maintain, using Puppet or Ansible is not les…

The future of Docker, Inc. is being an Oracle acquisition.

I can't believe I'm saying this, but if some giant corporation is going to buy Docker, Inc. then I really, really hope it's Microsoft. An Oracle acquisition would be an absolute nightmare.

Re: Docker for Mac with Kubernetes

#150

Post by guillaumerose »

theptip wrote: post #115
brown9-2 wrote: post #94

Earlier quoted context omitted.

I don’t get it either. minikube is trivially installed in my experience with homebrew. Given that running docker on a Mac has been a long and bumpy journey, I’m not sure I’d want to bundle the two together. What am I missing?

If I don't have to run minikube, and instead get something equivalent just by installing Docker for Mac, that's a minor win. If Docker's local Kubernetes install provides a way to connect to custom registries (e.g. GCR) without installing a third party plugin onto every minikube, I'd consider that a major win. https://github.com/kubernetes/minikube/blob/master/docs/inse...

Thanks for the suggestion. We will look at it.
Post reply on HN