Minikube: easily run Kubernetes locally • Hacker News Board

Re: Minikube: easily run Kubernetes locally

#11

Post by sofaofthedamned » Mon, Jul 11, 2016, 9:37 PM UTC

dlor wrote: post #10

sofaofthedamned wrote: post #6

Earlier quoted context omitted.

Another thing - the docs state to go to " rel="nofollow">https:// but that does nothing. Instead I have to go to http://kubernetesIP:30000 for the UI. Am I missing something else? Also, using the KVM driver on Ubuntu 16.04 I have to run the start command twice to be able to bring up a pod. That's with the 'vm-driver=kvm' at the end. Got there in the end anyways - thank you!

Hey, http://kubernetesIP/ui should work. Where in the docs did you see https://kubernetesIP ? I can get those cleaned up.

It's right in the app itself:

"$ minikube start Starting local Kubernetes cluster... Running pre-create checks... Creating machine... Starting local Kubernetes cluster... Kubernetes is available at https://192.168.99.100:8443."

Re: Minikube: easily run Kubernetes locally

#12

Post by sofaofthedamned » Mon, Jul 11, 2016, 9:45 PM UTC

dlor wrote: post #10

sofaofthedamned wrote: post #6

Earlier quoted context omitted.

Another thing - the docs state to go to " rel="nofollow">https:// but that does nothing. Instead I have to go to http://kubernetesIP:30000 for the UI. Am I missing something else? Also, using the KVM driver on Ubuntu 16.04 I have to run the start command twice to be able to bring up a pod. That's with the 'vm-driver=kvm' at the end. Got there in the end anyways - thank you!

Hey, http://kubernetesIP/ui should work. Where in the docs did you see https://kubernetesIP ? I can get those cleaned up.

In addition the VM isn't even listening on 80, it's only listening on 443 and 30000:

"Kubernetes is available at https://192.168.42.174:443. Kubectl is now configured to use the cluster. root@thinkbuntu:/root/kubernetes# nmap 192.168.42.174

Starting Nmap 7.01 ( https://nmap.org ) at 2016-07-11 22:44 BST Nmap scan report for 192.168.42.174 Host is up (0.00061s latency). Not shown: 996 closed ports PORT STATE SERVICE 22/tcp open ssh 443/tcp open https 8081/tcp open blackice-icecap 30000/tcp open unknown MAC Address: 52:54:00:C8:F1:38 (QEMU virtual NIC)

Nmap done: 1 IP address (1 host up) scanned in 25.54 seconds"

Re: Minikube: easily run Kubernetes locally

#13

Post by tupilaq » Tue, Jul 12, 2016, 8:32 AM UTC

I've used kid (https://github.com/vyshane/kid) to launch a docker based kubernetes environment on my laptop.

Means I don't have to use VirtualBox

Re: Minikube: easily run Kubernetes locally

#14

Post by mobiuscog » Tue, Jul 12, 2016, 8:36 AM UTC

dlor wrote: post #2

I'm an engineer working on Minikube. Feel free to ask about the tool here!

When will there be a windows version ?

Re: Minikube: easily run Kubernetes locally

#15

Post by rajeevsingh » Thu, Jul 14, 2016, 12:52 AM UTC

josephjacks wrote: post #8

Minikube is awesome! We used it at Apprenda in a recent K8s 101 webinar (0). Standing up a local K8s cluster in 1-2 minutes is a really great experience. (0): https://apprenda.wistia.com/medias/ckbmoa10sd

Great webinar! Kudos!

I set this up on my laptop and am noticing a strange behavior. When accessing the pod via http://192.168.99.100:30764/grid?cols=3&rows=5, all pods display the same ID. This means that the "NodePort" load-balancer is not performing round-robin load-balancing as expected. Any thoughts?

My environment: Macbook Pro, Intel i7, 16GB OS X (El Capitan 10.11.5) Docker for Mac (v1.12.0-rc3 client and server versions, https://www.docker.com/products/docker#/mac) kubectl v1.3.0 minikube v0.6.0

Re: Minikube: easily run Kubernetes locally

#16

Post by rajeevsingh » Thu, Jul 14, 2016, 6:49 PM UTC

rajeevsingh wrote: post #15

josephjacks wrote: post #8

Minikube is awesome! We used it at Apprenda in a recent K8s 101 webinar (0). Standing up a local K8s cluster in 1-2 minutes is a really great experience. (0): https://apprenda.wistia.com/medias/ckbmoa10sd

Great webinar! Kudos! I set this up on my laptop and am noticing a strange behavior. When accessing the pod via http://192.168.99.100:30764/grid?cols=3&rows=5 , all pods display the same ID. This means that the "NodePort" load-balancer is not performing round-robin load-balancing as expected. Any thoughts? My environment: Macbook Pro, Intel i7, 16GB OS X (El Capitan 10.11.5) Docker for Mac (v1.12.0-rc3 client and ser…

Nevermind. The root-cause seems to be aggressive browser caching.

Chrome and Safari display the same behavior i.e. all pod IDs the same.

Firefox displays different pod IDs (90% of the IDS are the same, however there are a few that are different)