9 ms·

Kubernetes 1.3 released

185 points by nkvoll 10y ago

crb 10y ago
1.3.0 is tagged, yes. The actual release (docs, release notes, etc) will happen early next week.
- jacques_chester 10y ago
  There's no karma in waiting on actual releases, friend.
- nkvoll 10y ago
  Not to get into a discussion regarding what constitutes a "Release" for any specific project, whether it's tagging, pushing, announcing[0], updating documentation, creating release notes, publish a release blog post and so on. A final build of 1.3 was tagged with an accompanying changelog and announcement post. I found it weird that it had no more ceremony, nor any prior submission on hn, and as it had been announced through the kubernetes-announce mailing list for 17 hours, I figured its existence would be interesting to the community, so I submitted it in good faith. In any case, kudos to everybody working on it and congratulations on the release, whether it's this week or the next. [0]: https://groups.google.com/forum/#!topic/kubernetes-announce/apb6bUfFsdc https://groups.google.com/forum/#!topic/kubernetes-announce/...
  - justinsb 10y ago
    I'm glad you posted it - thanks! My understanding is that with the timing of the US holiday, it made more sense to hold off on the official announcement for a few days. So that's why there aren't more announcements / release notes etc; and likely there won't be as many people around the community channels to help with any 1.3 questions this (long) weekend. You should expect the normal release procedure next week! And if you want to try it out you can, but most of the aspects of a release other than publishing the binaries are coming soon.
jackweirdy 10y ago
Wow, spooky coincidence - I discovered and installed this for the first time today! The docs could use some work, but generally pretty easy to get started. Great to see an openstack provider's been added, too.
- philips 10y ago
  Which guides did you use?
  - jackweirdy 10y ago
    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.
    - philips 10y ago
      minikube is awesome, really exciting development for the community. Which platform are you on?
      - jackweirdy 10y ago
        I'm on OSX, deploying to AWS - currently manually, potentially with Kubernetes soon!
esseti 10y ago
I run into kubernetes a week ago. Found out this: https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615 https://www.udacity.com/course/scalable-microservices-with-k... Sounds pretty interesting, especially all the part about service discovery & node health/replacement. Anyone using it for production?
- crb 10y ago
  We (Google) are :-) Otherwise, there's a list at http://kubernetes.io/community/ http://kubernetes.io/community/, including: New York Times, eBay, Wikimedia Foundation, Box, Soundcloud, Viacom, and Goldman Sachs, to name a few.
  - esseti 10y ago
    Duh, that's a nice list of references. I'll try to get trough the documentations and tutorial. It seems to solve a lot of troubles when we (normal people) have to deal when deploying docker container (in aws for example). Among others service discovery and health of nodes.
  - igmor 10y ago
    Don't you guys use Borg that I don't know how close to kubernetes?
- 010a 10y ago
  I didn't find that Udacity course all that helpful. Especially toward the end, where it could really shed some light on the actually advanced Kube topics, the videos shorten to 60 seconds each and he just glosses over topics without any explanation why they matter.
- arianvanp 10y ago
  This course is cringeworthily shallow. Short videos that don't go into details 'why' stuff happens. and people screaming 'WOW this is sooo useful' all the time without explainin why it's useful.
- esseti 10y ago
hnarayanan 10y ago
This is exciting. I need to update my Django Kubernetes tutorial (https://harishnarayanan.org/writing/kubernetes-django/ https://harishnarayanan.org/writing/kubernetes-django/) with some new constructs that simplify things.
- brianwawok 10y ago
  Django is about the perfect use case for a Kubernetes tutorial.. because it has enough moving parts that you need to do some trickery, but not 10 levels deep.
- drcongo 10y ago
  This is an excellent tutorial. Thanks!
EDevil 10y ago
Now if only a native Azure provider was developed it would be excellent...
- jmspring 10y ago
  The status of K8s on Azure is being updated here - https://github.com/colemickens/azure-kubernetes-status https://github.com/colemickens/azure-kubernetes-status
  - TheIronYuppie 10y ago
    Cole has been an absolute machine working on this - we'd love your help! Net, though, is that extending Kubernetes in this way is available to everyone - we support ~15 different cloud and OS configurations today, we'd love to support more! Disclosure: I work at Google on Kubernetes.
  - EDevil 10y ago
    Nice! I'll follow it and try to help as I can.
- brianwawok 10y ago
  Why would I want to take my perfectly nice VMs and run them on a windows server?
  - JeanMertz 10y ago
    Not sure if you are serious, but while Azure is from Microsoft, it is definitely not Windows only. In fact, most of the products coming out of the "new" Microsoft pipeline aren't in any way tied to Windows. Kudos to them, and awesome to see people working to get Kubernetes to work on Azure.
- colemickens 10y ago
  There's a working implementation here. I'm wrapping up cleanup + some unit tests before sending the PR. https://github.com/colemickens/kubernetes/tree/azure-cloudprovider https://github.com/colemickens/kubernetes/tree/azure-cloudpr... Not that it's very exciting to anyone who is familiar with Services + Pod networking, but there's a video demo: https://asciinema.org/a/48294 https://asciinema.org/a/48294
TheIronYuppie 10y ago
We are really proud of this release, both making it much easier to get started (with a laptop ready local development experience) as well as large scale enterprise features (support for stateful applications, IAM integration, 2x scale). As others in the thread mentioned, this was the cut of the binary, we'll be talking a lot more about it, updating docs and sharing customer stories in the coming weeks. Thanks, and please don't hesitate to let me know if you have any questions! Disclosure: I work at Google on Kubernetes.
- rue 10y ago
  > laptop ready local development experience The experience, definitely something I’m looking forward to, needs a lot of improvement if your laptop has an Apple logo on it. Hopefully some part of the team is working on that :)
  - dlor 10y ago
    Check out minikube, it's designed for running on laptops with Apple logos. :) https://github.com/kubernetes/minikube https://github.com/kubernetes/minikube Disclosure: I work at Google, on minikube.
  - deleted 10y ago
    [deleted]
- chrisgaun 10y ago
  The momentum and features are really unmatched compared to any comparable solution. Disclosure: I do not work at Google
philips 10y ago
Yea! The team at CoreOS is really excited about this release and the work that we have done as a community. If you are interested in some of the things that we helped get into this release see our "preview" blog post from a few weeks ago, RBAC, rkt container engine, simpler install, and more: https://coreos.com/blog/kubernetes-v1.3-preview.html https://coreos.com/blog/kubernetes-v1.3-preview.html
- thockingoog 10y ago
  The CoreOS team and technologies have been critical to getting Kubernetes going. Thanks, Brandon.
  - philips 10y ago
    At the risk of sounding like a mutual admiration society: Working with and learning from the folks in the community like Brian Grant, Dawn Chen, Joe Beda, Sarah Novotny, Brendan Burns, Daniel Smith, Mike Danese, Clayton Coleman, Eric Tune, Vish Kannan, David Oppenheimer, yourself Tim, and the hundreds of other folks in the community has been a great experience for me and the rest of the team at CoreOS. Can't wait to continue the success with v1.4!
- chrissnell 10y ago
  I can't imagine running Kubernetes without CoreOS. You guys make everything so easy for us (Revinate). Our systems infra workload for the CoreOS/Kubernetes cluster is a tiny fraction of what we spend on our Openstack gear.
jturolla 10y ago
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 the near future.
- chrissnell 10y ago
  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 build a completely self-service pipeline for our devs and has taken the ops team out of day-to-day app management. The nodes update themselves with the latest OS and Kube shifts the workload around as they do. This infrastructure is faster, more nimble, more cost-effective and so much easier to run. This is the best infrastructure I've ever used in twenty years of doing ops and leading ops teams.
  - TheIronYuppie 10y ago
    I can't agree more with others in the thread. This entire comment warms the cockles of my cold dead heart. I know Silicon Valley folks are infinitely pessimistic and/or grandiose, but this is LITERALLY the reason I got into this job. Disclosure: I work at Google on Kubernetes
  - thockingoog 10y ago
    You folks don't know how much it means to us to hear that people are finding success with Kubernetes. Thanks for using it. We'll try to keep pushing the envelope.
    - chrissnell 10y ago
kordless 10y ago
Interested in federated clusters. How is federation being scoped and who's doing most of the work on it?
- TheIronYuppie 10y ago
  Federation is a VERY big area. Your best bet is to start with the proposals: https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federation-high-level-arch.png https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federated-api-servers.md Though there are many issues in discussion. Anything in particular you want to work on? Disclosure: I work at Google on Kubernetes
smegel 10y ago
> 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?
- matthewrudy 10y ago
  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 https://github.com/kubernetes/kubernetes/pull/24464
- timdorr 10y ago
  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.
bogomipz 10y ago
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.
- thockingoog 10y ago
  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
  - bogomipz 10y ago
    Is it possible under specific circumstances such as if using LVM devices?
    - thockingoog 10y ago
      an LVM device is local, which is not supported as PersistentVolume. :(
      - bogomipz 10y ago
        Thats too bad it would be great to have an API for that. Mesos has the concept of path and mount disks, it would be neat if Kubernetes had something similar: http://mesos.apache.org/documentation/latest/multiple-disk/ http://mesos.apache.org/documentation/latest/multiple-disk/
        thockingoog 10y ago
        We do! it's just not a "persistent" volume because, well, it's not persistent...
qubit23 10y ago
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.
- thockingoog 10y ago
  It was so close, it just missed the boat. It will hopefully be on the next boat.
technofiend 10y ago
There was some coverage including labs at this week's RedHat Summit. Once all the materials are on line that may prove a useful 1.3 reference.
- TheIronYuppie 10y ago
  Our blog post is live! http://blog.kubernetes.io/2016/07/kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads.html http://blog.kubernetes.io/2016/07/kubernetes-1.3-bridging-cl... Disclosure: I work at Google on Kubernetes
lobster_johnson 10y ago
I'm really liking Kubernetes — we're in the process of migrating to it. If there's on area that is in dire need of improvement, though, it's the documentation. If you look around, there is essentially no documentation that starts from first principles, going through the different components (and their lifecycle, dependencies, requirements and so on) one by one, irrrespectively of the cloud environment. There is a "Kubernetes from scratch" [1] document, but it's just a bunch of loose fragments that lacks almost all the necessary detail, and has too many dependencies. (Tip: ask the user to install from source, and leave out how to use images, cloud providers and other things that obscure the workings of everything.) Almost all of the documentation assumes you're running kube-up or some other automated setup, which is of course convention, but hides a huge amount of magic in a bunch of shell scripts, Salt config and so on that prevents true understanding. If you run it for, say, AWS, then you'll end up with a configuration that you don't understand. It doesn't help that much of the official documentation is heavily skewed towards GCE/GKE, where certain things have a level of automatic magic that you won't benefit from when you run on bare metal, for example. kube-up will help someone get it up and running fast, but does not help someone who needs to maintain it in a careful, controller manner. Right now, I have a working cluster, but getting there involved a bunch of trial and error, a lot of open browser tabs, source code reading, and so on. (Quick, what version of Docker does Kubernetes want? Kubernetes doesn't seem to tell us, and it doesn't even verify it on startup. One of the reefs that I ran aground on was when 1.11 didn't work, and had to revert to 1.9, based on a random Github issue I found.) [1] http://kubernetes.io/docs/getting-started-guides/scratch/ http://kubernetes.io/docs/getting-started-guides/scratch/
- Rapzid 10y ago
  I can't agree with this enough. We are all on AWS and the level of effort it would take to migrate to Kubernetes while maintaining our ability to spin up complete ad-hoc environments on the fly(which also serves as continual DR testing) seems too much to justify at this point. Also, I can't come out the other side with just one or two people understanding, or having any hope of understanding, how everything works :| Likely if I had to choose today or this quarter we would go the empire route and build on top of ECS. Though, our model and requirements are a bit different so we'd have to heavily modify or roll our own.
Rapzid 10y ago
I'm still sitting on the sidelines waiting for the easy to install, better documented for AWS version. It's also a bit unclear as to why we are talking federation and master/slave in 2016; other systems are using raft and gossip protocols to build masterless management clusters.. Watching issues like https://github.com/kubernetes/kubernetes/issues/23478 https://github.com/kubernetes/kubernetes/issues/23478 , and https://github.com/kubernetes/kubernetes/issues/23174 https://github.com/kubernetes/kubernetes/issues/23174 .. I'm not super interested in "kicking the tires"; I'm evaluating replacing all our environment automation with a version built around Kubernetes. Easy-up scripts that hide a ton of nasty complexity won't do the trick. Following the issues I'm getting the impression that too much effort is being put into CM style tools vs making the underlying components more friendly to setup and manage. Did anyone see how easy it is to get the new Docker orchestration running? Then there is the AWS integration documentation.. I'm following the hidden aws_under_the_hood.md updates, but I'm still left with loads of questions; like how do I control the created ELB's configuration(cross zone load balancing, draining, timeouts,etc)? I re-evaluate after every update and there are some really nice features being added in, but at the end of the day ECS is looking more and more the direction to go for us. Sure, it's lacking a ton of features compared to Kubernetes and it's nigh but impossible to get any sort of information about roadmaps out of Amazon... But it's very clear how it integrates with ELB and how to manage the configuration of every underlying service. It also doesn't require extra resources(service or human) to setup and manage the scheduler.
- TheIronYuppie 10y ago
  Can you say more about the complexity you're worried about? The projects you mention WILL land in 1.4 (which is about 90 days away), and thousands of companies are running huge production deployments on AWS, GCP, Azure, OpenStack and on-premises. Further, plug-ins already exist for Chef, Puppet, Salt and Ansible, if you'd like to use them. To be clear, nothing is "masterless" - please go check out the production deployments for other container management solutions, they all require a separate control plane when running in production with a cluster of any reasonable (>64 nodes) size. FYI, it's a best practice when running a cluster of any size to separate the control plane. To your direct question, with the other orchestration tools, how would you manage your ELB? Wouldn't you have your own management? They don't (to the best of my knowledge) do any sort of integration - not even the minimum level that Kubernetes does. Disclosure: I work at Google on Kubernetes
dankohn1 10y ago
I'm looking for startups that are using Kubernetes in production who would like some free publicity. I'm the new executive director of the Cloud Native Computing Foundation, which hosts Kubernetes. We have end user members like eBay, Goldman Sachs and NCSoft, but we're in need of startup end users (as opposed to startup vendors, of which we have many). Please reach out to me at dan at linuxfoundation.org if you might like to be featured in a case study.
nikon 10y ago
Awesome. Just digging into Docker and have recently been reading about Kubernetes. Does anyone have examples of how they are managing deployments? I.e. deploying app update, running db migrations perhaps?

185 points by nkvoll 10y ago

crb 10y ago

1.3.0 is tagged, yes. The actual release (docs, release notes, etc) will happen early next week.

jacques_chester 10y ago
There's no karma in waiting on actual releases, friend.
nkvoll 10y ago
Not to get into a discussion regarding what constitutes a "Release" for any specific project, whether it's tagging, pushing, announcing[0], updating documentation, creating release notes, publish a release blog post and so on. A final build of 1.3 was tagged with an accompanying changelog and announcement post. I found it weird that it had no more ceremony, nor any prior submission on hn, and as it had been announced through the kubernetes-announce mailing list for 17 hours, I figured its existence would be interesting to the community, so I submitted it in good faith. In any case, kudos to everybody working on it and congratulations on the release, whether it's this week or the next. [0]: https://groups.google.com/forum/#!topic/kubernetes-announce/apb6bUfFsdc https://groups.google.com/forum/#!topic/kubernetes-announce/...
- justinsb 10y ago
  I'm glad you posted it - thanks! My understanding is that with the timing of the US holiday, it made more sense to hold off on the official announcement for a few days. So that's why there aren't more announcements / release notes etc; and likely there won't be as many people around the community channels to help with any 1.3 questions this (long) weekend. You should expect the normal release procedure next week! And if you want to try it out you can, but most of the aspects of a release other than publishing the binaries are coming soon.

jackweirdy 10y ago

Wow, spooky coincidence - I discovered and installed this for the first time today! The docs could use some work, but generally pretty easy to get started. Great to see an openstack provider's been added, too.

philips 10y ago
Which guides did you use?
- jackweirdy 10y ago
  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.
  - philips 10y ago
    minikube is awesome, really exciting development for the community. Which platform are you on?
    - jackweirdy 10y ago
      I'm on OSX, deploying to AWS - currently manually, potentially with Kubernetes soon!

esseti 10y ago

I run into kubernetes a week ago. Found out this: https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615 https://www.udacity.com/course/scalable-microservices-with-k... Sounds pretty interesting, especially all the part about service discovery & node health/replacement. Anyone using it for production?

crb 10y ago
We (Google) are :-) Otherwise, there's a list at http://kubernetes.io/community/ http://kubernetes.io/community/, including: New York Times, eBay, Wikimedia Foundation, Box, Soundcloud, Viacom, and Goldman Sachs, to name a few.
- esseti 10y ago
  Duh, that's a nice list of references. I'll try to get trough the documentations and tutorial. It seems to solve a lot of troubles when we (normal people) have to deal when deploying docker container (in aws for example). Among others service discovery and health of nodes.
- igmor 10y ago
  Don't you guys use Borg that I don't know how close to kubernetes?
010a 10y ago
I didn't find that Udacity course all that helpful. Especially toward the end, where it could really shed some light on the actually advanced Kube topics, the videos shorten to 60 seconds each and he just glosses over topics without any explanation why they matter.
arianvanp 10y ago
This course is cringeworthily shallow. Short videos that don't go into details 'why' stuff happens. and people screaming 'WOW this is sooo useful' all the time without explainin why it's useful.
esseti 10y ago

hnarayanan 10y ago

This is exciting. I need to update my Django Kubernetes tutorial (https://harishnarayanan.org/writing/kubernetes-django/ https://harishnarayanan.org/writing/kubernetes-django/) with some new constructs that simplify things.

brianwawok 10y ago
Django is about the perfect use case for a Kubernetes tutorial.. because it has enough moving parts that you need to do some trickery, but not 10 levels deep.
drcongo 10y ago
This is an excellent tutorial. Thanks!

EDevil 10y ago

Now if only a native Azure provider was developed it would be excellent...

jmspring 10y ago
The status of K8s on Azure is being updated here - https://github.com/colemickens/azure-kubernetes-status https://github.com/colemickens/azure-kubernetes-status
- TheIronYuppie 10y ago
  Cole has been an absolute machine working on this - we'd love your help! Net, though, is that extending Kubernetes in this way is available to everyone - we support ~15 different cloud and OS configurations today, we'd love to support more! Disclosure: I work at Google on Kubernetes.
- EDevil 10y ago
  Nice! I'll follow it and try to help as I can.
brianwawok 10y ago
Why would I want to take my perfectly nice VMs and run them on a windows server?
- JeanMertz 10y ago
  Not sure if you are serious, but while Azure is from Microsoft, it is definitely not Windows only. In fact, most of the products coming out of the "new" Microsoft pipeline aren't in any way tied to Windows. Kudos to them, and awesome to see people working to get Kubernetes to work on Azure.
colemickens 10y ago
There's a working implementation here. I'm wrapping up cleanup + some unit tests before sending the PR. https://github.com/colemickens/kubernetes/tree/azure-cloudprovider https://github.com/colemickens/kubernetes/tree/azure-cloudpr... Not that it's very exciting to anyone who is familiar with Services + Pod networking, but there's a video demo: https://asciinema.org/a/48294 https://asciinema.org/a/48294

TheIronYuppie 10y ago

We are really proud of this release, both making it much easier to get started (with a laptop ready local development experience) as well as large scale enterprise features (support for stateful applications, IAM integration, 2x scale). As others in the thread mentioned, this was the cut of the binary, we'll be talking a lot more about it, updating docs and sharing customer stories in the coming weeks. Thanks, and please don't hesitate to let me know if you have any questions! Disclosure: I work at Google on Kubernetes.

rue 10y ago
> laptop ready local development experience The experience, definitely something I’m looking forward to, needs a lot of improvement if your laptop has an Apple logo on it. Hopefully some part of the team is working on that :)
- dlor 10y ago
  Check out minikube, it's designed for running on laptops with Apple logos. :) https://github.com/kubernetes/minikube https://github.com/kubernetes/minikube Disclosure: I work at Google, on minikube.
- deleted 10y ago
  [deleted]
chrisgaun 10y ago
The momentum and features are really unmatched compared to any comparable solution. Disclosure: I do not work at Google

philips 10y ago

Yea! The team at CoreOS is really excited about this release and the work that we have done as a community. If you are interested in some of the things that we helped get into this release see our "preview" blog post from a few weeks ago, RBAC, rkt container engine, simpler install, and more: https://coreos.com/blog/kubernetes-v1.3-preview.html https://coreos.com/blog/kubernetes-v1.3-preview.html

thockingoog 10y ago
The CoreOS team and technologies have been critical to getting Kubernetes going. Thanks, Brandon.
- philips 10y ago
  At the risk of sounding like a mutual admiration society: Working with and learning from the folks in the community like Brian Grant, Dawn Chen, Joe Beda, Sarah Novotny, Brendan Burns, Daniel Smith, Mike Danese, Clayton Coleman, Eric Tune, Vish Kannan, David Oppenheimer, yourself Tim, and the hundreds of other folks in the community has been a great experience for me and the rest of the team at CoreOS. Can't wait to continue the success with v1.4!
chrissnell 10y ago
I can't imagine running Kubernetes without CoreOS. You guys make everything so easy for us (Revinate). Our systems infra workload for the CoreOS/Kubernetes cluster is a tiny fraction of what we spend on our Openstack gear.

jturolla 10y ago

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 the near future.

chrissnell 10y ago
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 build a completely self-service pipeline for our devs and has taken the ops team out of day-to-day app management. The nodes update themselves with the latest OS and Kube shifts the workload around as they do. This infrastructure is faster, more nimble, more cost-effective and so much easier to run. This is the best infrastructure I've ever used in twenty years of doing ops and leading ops teams.
- TheIronYuppie 10y ago
  I can't agree more with others in the thread. This entire comment warms the cockles of my cold dead heart. I know Silicon Valley folks are infinitely pessimistic and/or grandiose, but this is LITERALLY the reason I got into this job. Disclosure: I work at Google on Kubernetes
- thockingoog 10y ago
  You folks don't know how much it means to us to hear that people are finding success with Kubernetes. Thanks for using it. We'll try to keep pushing the envelope.
  - chrissnell 10y ago

kordless 10y ago

Interested in federated clusters. How is federation being scoped and who's doing most of the work on it?

TheIronYuppie 10y ago
Federation is a VERY big area. Your best bet is to start with the proposals: https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federation-high-level-arch.png https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federated-api-servers.md Though there are many issues in discussion. Anything in particular you want to work on? Disclosure: I work at Google on Kubernetes

smegel 10y ago

> 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?

matthewrudy 10y ago
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 https://github.com/kubernetes/kubernetes/pull/24464
timdorr 10y ago
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.

bogomipz 10y ago

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.

thockingoog 10y ago
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
- bogomipz 10y ago
  Is it possible under specific circumstances such as if using LVM devices?
  - thockingoog 10y ago
    an LVM device is local, which is not supported as PersistentVolume. :(
    - bogomipz 10y ago
      Thats too bad it would be great to have an API for that. Mesos has the concept of path and mount disks, it would be neat if Kubernetes had something similar: http://mesos.apache.org/documentation/latest/multiple-disk/ http://mesos.apache.org/documentation/latest/multiple-disk/
      - thockingoog 10y ago
        We do! it's just not a "persistent" volume because, well, it's not persistent...

qubit23 10y ago

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.

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

technofiend 10y ago

There was some coverage including labs at this week's RedHat Summit. Once all the materials are on line that may prove a useful 1.3 reference.

TheIronYuppie 10y ago
Our blog post is live! http://blog.kubernetes.io/2016/07/kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads.html http://blog.kubernetes.io/2016/07/kubernetes-1.3-bridging-cl... Disclosure: I work at Google on Kubernetes

lobster_johnson 10y ago

I'm really liking Kubernetes — we're in the process of migrating to it. If there's on area that is in dire need of improvement, though, it's the documentation. If you look around, there is essentially no documentation that starts from first principles, going through the different components (and their lifecycle, dependencies, requirements and so on) one by one, irrrespectively of the cloud environment. There is a "Kubernetes from scratch" [1] document, but it's just a bunch of loose fragments that lacks almost all the necessary detail, and has too many dependencies. (Tip: ask the user to install from source, and leave out how to use images, cloud providers and other things that obscure the workings of everything.) Almost all of the documentation assumes you're running kube-up or some other automated setup, which is of course convention, but hides a huge amount of magic in a bunch of shell scripts, Salt config and so on that prevents true understanding. If you run it for, say, AWS, then you'll end up with a configuration that you don't understand. It doesn't help that much of the official documentation is heavily skewed towards GCE/GKE, where certain things have a level of automatic magic that you won't benefit from when you run on bare metal, for example. kube-up will help someone get it up and running fast, but does not help someone who needs to maintain it in a careful, controller manner. Right now, I have a working cluster, but getting there involved a bunch of trial and error, a lot of open browser tabs, source code reading, and so on. (Quick, what version of Docker does Kubernetes want? Kubernetes doesn't seem to tell us, and it doesn't even verify it on startup. One of the reefs that I ran aground on was when 1.11 didn't work, and had to revert to 1.9, based on a random Github issue I found.) [1] http://kubernetes.io/docs/getting-started-guides/scratch/ http://kubernetes.io/docs/getting-started-guides/scratch/

Rapzid 10y ago
I can't agree with this enough. We are all on AWS and the level of effort it would take to migrate to Kubernetes while maintaining our ability to spin up complete ad-hoc environments on the fly(which also serves as continual DR testing) seems too much to justify at this point. Also, I can't come out the other side with just one or two people understanding, or having any hope of understanding, how everything works :| Likely if I had to choose today or this quarter we would go the empire route and build on top of ECS. Though, our model and requirements are a bit different so we'd have to heavily modify or roll our own.

Rapzid 10y ago

I'm still sitting on the sidelines waiting for the easy to install, better documented for AWS version. It's also a bit unclear as to why we are talking federation and master/slave in 2016; other systems are using raft and gossip protocols to build masterless management clusters.. Watching issues like https://github.com/kubernetes/kubernetes/issues/23478 https://github.com/kubernetes/kubernetes/issues/23478 , and https://github.com/kubernetes/kubernetes/issues/23174 https://github.com/kubernetes/kubernetes/issues/23174 .. I'm not super interested in "kicking the tires"; I'm evaluating replacing all our environment automation with a version built around Kubernetes. Easy-up scripts that hide a ton of nasty complexity won't do the trick. Following the issues I'm getting the impression that too much effort is being put into CM style tools vs making the underlying components more friendly to setup and manage. Did anyone see how easy it is to get the new Docker orchestration running? Then there is the AWS integration documentation.. I'm following the hidden aws_under_the_hood.md updates, but I'm still left with loads of questions; like how do I control the created ELB's configuration(cross zone load balancing, draining, timeouts,etc)? I re-evaluate after every update and there are some really nice features being added in, but at the end of the day ECS is looking more and more the direction to go for us. Sure, it's lacking a ton of features compared to Kubernetes and it's nigh but impossible to get any sort of information about roadmaps out of Amazon... But it's very clear how it integrates with ELB and how to manage the configuration of every underlying service. It also doesn't require extra resources(service or human) to setup and manage the scheduler.

TheIronYuppie 10y ago
Can you say more about the complexity you're worried about? The projects you mention WILL land in 1.4 (which is about 90 days away), and thousands of companies are running huge production deployments on AWS, GCP, Azure, OpenStack and on-premises. Further, plug-ins already exist for Chef, Puppet, Salt and Ansible, if you'd like to use them. To be clear, nothing is "masterless" - please go check out the production deployments for other container management solutions, they all require a separate control plane when running in production with a cluster of any reasonable (>64 nodes) size. FYI, it's a best practice when running a cluster of any size to separate the control plane. To your direct question, with the other orchestration tools, how would you manage your ELB? Wouldn't you have your own management? They don't (to the best of my knowledge) do any sort of integration - not even the minimum level that Kubernetes does. Disclosure: I work at Google on Kubernetes

dankohn1 10y ago

I'm looking for startups that are using Kubernetes in production who would like some free publicity. I'm the new executive director of the Cloud Native Computing Foundation, which hosts Kubernetes. We have end user members like eBay, Goldman Sachs and NCSoft, but we're in need of startup end users (as opposed to startup vendors, of which we have many). Please reach out to me at dan at linuxfoundation.org if you might like to be featured in a case study.

nikon 10y ago

Awesome. Just digging into Docker and have recently been reading about Kubernetes. Does anyone have examples of how they are managing deployments? I.e. deploying app update, running db migrations perhaps?