Kubernetes is becoming the de-facto orchestration for managing container clustering services. Modern development teams dedicated to microservices-based application architectures feel their IT department isn’t moving fast enough and the innovation discovery pressures they are working under given the product competition they face. They tend to become “Shadow IT” where creating a container cluster on a public cloud becomes additional “work” for them rather than developing code. Now, all developers have to do is point their existing CI/CD toolchains to a Kubernetes cluster provided to them by their newest, most favorite friends in IT with the knowledge that it is backed not just by Cisco but by Google as well. No more cluster maintenance taking up hours that you could be spending on new functionality. No more hassles over Shadow IT. Less friction, more innovation.
The Cisco Container Platform distribution provided as part of the solution is the exact version of the exact distribution with the exact configurations used by the Google Kubernetes Engine (GKE), their public cloud hosted managed container clustering service. No long discussions over what should or should not be included or how it should be configured. Cisco hasn’t made those decisions, Google has—and nobody has been running container clusters longer than they have. And it doesn’t have to be just Google Cloud. Amazon AWS and Microsoft Azure can also be leveraged.
Cisco has partnered with Amazon, Google and Microsoft to provide a hybrid solution that includes your on-premises datacenter and accessibility to their cloud environments through a single “plane of glass.” It’s super easy to install on-premises and spins up a container cluster in a few minutes. We’ve also included Contiv so that container networking can be managed with profiles and, optionally, can be connected to Cisco ACI so that a network administrator can manage bare metal, VMs, and now, containers, all from the same place.