News for hackers. Stuff that matters.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by TheIronYuppie on Wednesday July 06, 2016 @12:41PM (#12044239)
Yep! For those that haven't seen it - https://github.com/kubernetes/minikube It's really cool - even runs a FULL UI locally (minikube dashboard), and supports xhyve, virtualbox, KVM and VMWare Fusion.

TL;DR

  # For Mac
  $ curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.4.0/minikube-darwin-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
  # For Linux
  curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.4.0/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
  $ minikube start
  $ (99% of regular kubernetes commands here)
Disclosure: I work at Google on Kubernetes.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by JustinGarrison on Wednesday July 06, 2016 @12:52PM (#12044317)
Why does minikube use a VM layer on Linux? Is it just for flexibility and not using the local docker daemon?
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by dlor on Wednesday July 06, 2016 @12:58PM (#12044374)
We mainly use the VM to provide a well-known and tested environment for Kubernetes to run in. Running inside a Docker container on Linux would have similar benefits, but there are still a few bugs with running some of the Kubernetes components inside containers.

We'll probably add a "native" option for Linux at some point. See this issue: https://github.com/kubernetes/minikube/issues/261 for a little more conversation.

Disclosure: I work at Google, on Minikube.

Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by NetStrikeForce on Wednesday July 06, 2016 @01:02PM (#12044406)
This is very cool, finally I don't need a datacentre to test some things :)

thanks!

Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by moosingin3space on Wednesday July 06, 2016 @01:33PM (#12044612)
I don't know if this is why, but when I work with Docker on Linux, I prefer to use docker-machine's VM layer because that way, I don't need to run docker commands as root.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by JustinGarrison on Wednesday July 06, 2016 @01:42PM (#12044667)
My only complaint with the VM layer is it's harder to have faster iterations with local development. I know this isn't the documented way to develop with kubernetes but I often use containers with -v $PWD:/app to test things interactively
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by moosingin3space on Wednesday July 06, 2016 @02:43PM (#12045026)
Ahh, now that makes sense. I don't usually develop inside a container, so that's why I haven't had this issue before.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by hosh on Wednesday July 06, 2016 @04:15PM (#12045577)
That's how I usually work with my code on local development.
Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by raesene6 on Wednesday July 06, 2016 @01:17PM (#12044507)
That's pretty cool, as some of the Kubernetes installation procedures can look a little daunting.

One question though, are there any plans to support Windows as a host OS for this (either via VMWare Workstation or Hyper-V directly, or via something like Vagrant)?

Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by avtar on Wednesday July 06, 2016 @01:36PM (#12044640)
I was curious about this as well:

https://github.com/kubernetes/minikube/issues/28

Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by TheIronYuppie on Wednesday July 06, 2016 @06:35PM (#12046334)
Heh - this is now out of date (we move fast!)

Rather than linking to the new command, here's a list of all the releases, with instructions:

https://github.com/kubernetes/minikube/releases

Re:Announcing Kubernetes 1.3: Bridging Cloud Native and Ente... by felixgallo on Wednesday July 06, 2016 @04:17PM (#12045599)
you linked to the 0.4.0 version, but apparently there's a 0.5.0 version now; replacing 0.4.0 with 0.5.0 worked for me, and 0.5.0 seems to work better on osx 10.10.