someone from knative please explain. k8s has forever championed the pod as the best things since sliced bread. so why does knative eschew the pod and only allow a container?
-
-
Replying to @ibuildthecloud
Because that would mean passing through a kubernetes construct to serverless user? Just guessing but that feels right to me.
1 reply 0 retweets 2 likes -
Replying to @aronchick
That's what I'm trying to understand. Basically is knative really only designed for functions? Builds, eventing, routing, config versioning all those features only for functions? Seems it could be more generally useful. In the end I see a lot of odd design choices.
1 reply 0 retweets 3 likes -
Replying to @ibuildthecloud @aronchick
/cc
@mchmarny who may have an answer1 reply 0 retweets 0 likes -
Container is the unit developers use to deploy workloads. At runtime it is still a pod. Devs get the request based autoscaling, including scaling to 0 pods when not used...
2 replies 0 retweets 1 like
Yes, activation and scaling would be more complicated with multiple containers. Simpler is the main point. Multiple containers can still be used under the hood, such as for proxies.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.