Live data from Hacker News

Kubernetes 1.3 released

github.com

31–40 of 94 posts

Re: Kubernetes 1.3 released

#32
post #29

Earlier quoted context omitted.

Only the docs on the website (barring a 5 minute intro to the "Why" of kubernetes[0]). Used the docs for getting set up locally with minikube, and also the hello node example.

minikube is awesome, really exciting development for the community. Which platform are you on?

I'm on OSX, deploying to AWS - currently manually, potentially with Kubernetes soon!

Re: Kubernetes 1.3 released

#33
post #31

> AWS > Support for ap-northeast-2 region (Seoul) What does this mean? How can K8S be tied into something as specific as an AWS region?

It means the `kube-up` scripts now work with ap-northeast-2 straight out of the box.

Just set

    export KUBERNETES_PROVIDER=aws
    export KUBE_AWS_ZONE=ap-northeast-2a
    kube-up.sh
Here's the PR https://github.com/kubernetes/kubernetes/pull/24464

Re: Kubernetes 1.3 released

#34
post #31

> AWS > Support for ap-northeast-2 region (Seoul) What does this mean? How can K8S be tied into something as specific as an AWS region?

Kubernetes can be installed from AMIs, which are region-specific.

In addition, different regions support different AWS features/products and being a newer region usually means the least amount of support. So any setup tooling or infrastructure integration needs to account for those differences and use alternatives if certain services aren't available.

Re: Kubernetes 1.3 released

#35

Really amazed by their great work. I'll look forward to upgrade the setup at my company. Since we started using kubernetes, we reduced our bill to 30% of its original price, and it made everything easier and scalable just as if we were using the costy Heroku. It's a really useful tech for third-world startups that cannot afford to spend thousands of dollars on infraestructure. I hope I can contribute to this OSS in t…

We've seen similar savings at our company. We have deployed Kube on a 6-node cluster of CoreOS nodes with 512GB each. These are dedicated servers hosted at Rackspace. We're about 30-40% utilized on RAM and maybe 15-20% on CPU. To host a similar set of services on our older Openstack environment would require at least 2-3x the number of servers. The cost savings isn't even the best part. Kubernetes has allowed us to b…

Have you compared the cost of maintaining your own CoreOS infrastructure at RAX just for kubernetes to using Googles Container Engine? If your services are all containerized and deployed via k8s to begin with, seems like you wouldn't have much reason to maintain your own infra at that point.

Re: Kubernetes 1.3 released

#36
Does anybody know how 1.3 is for stateless services? Can I use an API to crete a persistent disk volume and adjust that volume size just as I would any other resource like CPU, memory? The use case being postgres/mysql instances.

Re: Kubernetes 1.3 released

#37
One feature I was hoping to see in this release was the ScheduledJobs controller. I remember seeing it mentioned in one of the RCs; did it get pushed back? This would be useful for those of us who want a more highly available cron-like system running on top of Kubernetes.

Re: Kubernetes 1.3 released

#39
post #37

One feature I was hoping to see in this release was the ScheduledJobs controller. I remember seeing it mentioned in one of the RCs; did it get pushed back? This would be useful for those of us who want a more highly available cron-like system running on top of Kubernetes.

It was so close, it just missed the boat. It will hopefully be on the next boat.

Re: Kubernetes 1.3 released

#40

Does anybody know how 1.3 is for stateless services? Can I use an API to crete a persistent disk volume and adjust that volume size just as I would any other resource like CPU, memory? The use case being postgres/mysql instances.

You can't, in general, adjust the size of block devices purely transparently. We don't currently support blockdev resizing. Would love to talk about how to achieve that, though
Post reply on HN