Thanks to all who joined us for the Platform9 2017 Container and Cloud Orchestration Report Webinar: The Evolution of the Cloud: Why Containers and Kubernetes are the Next Big Steps, where Platform9 discussed the popularity of containers, how they can factor into your DevOps strategy and why a SaaS-managed solution provides a balanced answer to your container environment. After the webinar, we took questions from the audience but unfortunately ran out of time before we could answer everybody’s questions. You can read the full Q&A below.
What about VMs? Why use containers over VMs?
Containers provide the ability to package all of an application’s dependencies into an isolated and lightweight deployment.
What makes Kubernetes better compared to some other container orchestration solutions?
The key differentiation is that Kubernetes brings a rich history of lessons-learned internally at Google, over the past decade, orchestrating production containerized workloads at scale. Kubernetes is an open framework that will protect against closed & proprietary orchestration solutions as well as dependent ecosystems.
What is required to run Platform9 Managed Kubernetes?
Dedicated physical servers or virtual machines running Linux for on-premise. Additionally Platform9 supports a bring-your-own-credentials model for public cloud deployments.
Can the node that form part of a cluster be a mix of on-premise and Public cloud such as AWS, Azure etc.
Sort of. There is a capability known as Federations of Kubernetes Clusters, that can include clusters running in different cloud providers (e.g. Google Cloud, AWS), and on-premises (e.g. on OpenStack). In a Federation deployment one would create all of the clusters that are required, in the appropriate cloud providers and/or locations. Thereafter, your API resources can span different clusters and cloud providers.
Could you provide key difference between Orchestration platforms – Kubernetes, MESOS?
Are there any Open Source monitoring solutions for K8S?
Heapster is a cluster-wide aggregator of monitoring and event data. It currently supports Kubernetes natively and works on all Kubernetes setups. https://prometheus.io/.
Will you be able to manage deployments on client ‘s on-premise environment?
Yes. On-premise and bring-your-own cloud credentials deployment models are supported today.
How do you position Cloud Foundry and K8S?
CloudFoundry’s primary audience is enterprise application devs who want to deploy 12-factor stateless apps using Heroku-style buildpacks. Kubernetes’ audience is a little broader, including both stateless application and stateful service developers can provide their own containers.
If we opt for SaaS model will our admins have access to the platform?
Platform9 users can make operational decisions on who can access the User Interface, this can be an admin or operations team. There are also a number of methods to provide access to Kubernetes clusters that are under management.
Considering a scenario with only on prem nodes, what happens when not if my internet connection goes down for whatever reason, can I fall back on something local or it’s back to the stone age? I’m asking this from more of an enterprise perspective.
For on-prem K8S cluster, loss of internet connectivity to the Platform9 control plane will not take down the cluster. Loss of internet connectivity could affect services running in the on-prem cluster that depend on internet access.
Is it possible to get a hands on experience on your platform?
Does the PF9 service work for Cloud and Managed service providers? (specifically role based permission controls, to segregate the customers from Ops, as well as supporting customers who act as re-sellers/brokers themselves..)
Yes. There are a number of ways to integrate Platform9 solutions into MSP or Reseller models with tenants and roles.