We're just in the process of spinning up a multitenancy working group. How would you feel about rolling virtual kubelet into that group, rather than starting a new group?
On Thu, Dec 14, 2017 at 2:35 PM, 'Ria Bhatia' via Kubernetes user discussion and Q&A <[email protected]> wrote: > Hi Everyone! > > > > I'm Ria Bhatia, a Program Manager within Microsoft Azure. I work on Azure > Container Instances (ACI) but specifically I've been working on the ACI > Connector. The connector allows customers to spin out container instances > from their Kubernetes clusters, which gives them the benefits of per second > billing and virtually unlimited compute resources. We've already seen a lot > of interest from customers because they don't want to manage their worker > nodes, but instead they want to focus on building and deploying their > containerized applications. The possibility of eliminating the need to > manage agents, not just masters, is exciting and wanted by customers. > > > > After releasing ACI we saw a shift in the cloud market, with Hyper.sh > forking off our ACI Connector code, and then Amazon releasing Fargate, > which is their version of container instances within the cloud. We realized > there was an opportunity to help the other cloud providers connect their > pods as a service, platforms, to clusters. Therefore we released a new > community and pluggable version of the ACI Connector, named > Virtual Kubelet and it's currently hosted here: https://github.com/ > virtual-kubelet/virtual-kubelet > > > > As a result, I'm proposing for the creation of a "Virtual Kubelet" working > group where all relevant cloud providers and interested parties can help > guide and design the future of "serverless" Kubernetes. Through > Virtual Kubelet we can conform on the design for how customers will > interact and create applications that directly deploy to Kubernetes without > any extra thought on the underlying infrastructure. > > > > Mission statement: Design and build a consensus around how users interact > with pods as the base layer of infrastructure within Kubernetes. Create an > experience so all cloud providers have a consistent and innovative > interface for connecting Kubernetes to their pods as a service, > platforms. > > > > Thanks, > > Ria > > > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
