isdal

3 ms·

1. 1.▲
   by isdal 8y ago

   Yep, no free lunch. Scaling up has a few different "cliffs". To outline a few: 1. Existing pod scheduled and ready (fastest) 2. Room on existing node (so no docker pull needed) 3. Room on existing cluster (so no VM creation needed
2. 2.▲
   by isdal 8y ago

   Thanks! In my mind a key goal for Knative is to: "Free customers from serverless lock-in through industry-wide portability" I think I like your version better so maybe I should start using that :-) We are still very early in the p
3. 3.▲
   by isdal 8y ago

   Knative depends on Kubernetes and should run well on any reasonable Kubernetes setup. I haven't tested Knative on AWS since I'm not a customer there :-) We were thrilled to see Microsoft contribute instructions for Azure ( https:&
4. 4.▲
   by isdal 8y ago

   Network/Load-balancer programming is embarrassingly slow on Flex. We have long term projects in place that will improve it but I can't give any dates here. Short term we have a few tactical features in the pipeline. In the next fe
5. 5.▲
   by isdal 8y ago

   I'm the engineering manager at Google responsible for both Knative and App Engine Flex. What we heard from a lot of customers is that they want a serverless / App Engine Flex-like experience but one that works multi-cloud or in hy
6. 6.▲
   by isdal 8y ago

   The github page is now public. If you want to see the actual code you can find it at https://github.com/knative