4 ms·
Google's response went way beyond my expectations here.
by zwischenzug 12y ago
Google's response went way beyond my expectations here.
- otoburb 12y agoI didn't see anything in your blog post that refers to a response from Google. Could you elaborate on that? Thanks!
- zwischenzug 12y ago"I tried to follow Kubernetes’ Vagrant stand-up, but got frustrated with its slow pace and clunkiness, which I characterized uncharitably as ‘soviet’. Amazingly, a Twitter-whinge about this later and I got a message from the Kubernetes Lead Engineer saying they were ‘working on it’. " I'll try and make this clearer - thanks for the feedback!
- chuhnk 12y agoHad similar pain points 6 months ago. Went through vagrant, docker, ec2, gce, gke and found issues almost everywhere. That's just the way it goes in the early days. 6-12 months down the line this will all be really easy and seamless with hopefully a lot more people contributing to the kubernetes ecosystem.
- zwischenzug 12y agoGlad it wasn't just me... I did waste a lot of time 'researching' Kubernetes this way.
- brendandburns 12y agoI updated it over the weekend, it's down to 3 steps now: https://github.com/brendandburns/kubernetes/blob/hyperkube/docs/getting-started-guides/docker.md https://github.com/brendandburns/kubernetes/blob/hyperkube/d... And I think I can get it down to a one-liner. (also, can you update your blog to point to the hyperkube:v0.14.1 image instead of :dev, :dev is a random binary from my client, where as v0.14.1 is an official release... Thanks!)
- ossreality 12y agoOpenShift has an Openshift-in-a-box-container that includes Kubernetes.
- zwischenzug 12y agoDone! You caught me just before sleep.
- mdekkers 12y agoI have also tried kubernetes a few times, and got stuck everywhere. I was unable to find a "this is how you build a kubernetes system from scratch" document somewhere. All I managed to find where very specific howto's for specific system combinations, none of which fits my needs. I tried a few times with building systems on the documentation list, but ran into issues at each step. My biggest worry and issue with running kubernetes in production is the overall workflow of standing up an environment, which seems to be: 1. download some images/dockerfiles 2. [magic] 3. profit I cannot find a document anywhere that tells me what components are used, how they interact, what settings are required, etc. I'd love to be able to give kubernetes a try and see how it would work for our service, but am having a very hard time getting the right level of detail. It appears to be either "go the [magic] route", or "read all the code" with little in between. If I had some kind of pointer, I'd be happy to write something up about how to get it running for a prod setup...
- zwischenzug 12y agoI think it's too early for you to think about Kub in production by the sounds of it. This whole area is still in the early stages; any documentation you see on specifics are likely to be soon out of date. If you try the hyperkube command you'll see very many command line options, and I can only see that growing. To an extent though, there is a certain amount of magic when downloading images that do stuff for you. For example, the scheduler is a pod that just starts up on the master. What exactly it does, I've no idea yet. To quote the kub github page: "Kubernetes is in pre-production beta! While the concepts and architecture in Kubernetes represent years of experience designing and building large scale cluster manager at Google, the Kubernetes project is still under heavy development. Expect bugs, design and API changes as we bring it to a stable, production product over the coming year."