the vSphere-Tanzu combo does not need to run the complete stack. “They can bring their own networking, they can bring their own storage,” D’Paiva explained, adding that it should also accelerate modern workload transformations because it ties directly into the vSphere platform that many enterprises are already running today.
“With this drop-in infrastructure it takes about an hour for an existing IT administrator to simply get started with Kubernetes and go,” D’Paiva said.
Because of lack of skills, they setup a team (named Stratus) to centralize [and also market?] the new platform.
(~4:10) – Building a centralized, standardized platform is important for efficiencies (reducing duplicated efforts) but also governance and maintainability, long-term. “We are building a solid container platform. Why would a team not do it themselves? If you have about 600 teams that want to use containers and everyone would need to build their own unique container platform, it would become unmanageable as a company you cannot control it, and it would be a lot of reinventing the wheel.” MS-Word dictation transcription: And that’s something you don’t want because then things are wasting, the team’s time, the valuable time so therefore it would be good if one team would build a strong foundation or the other teams can build on top of that. Also need to enforce policies/governance/security on the team’s work.
They do the typical platform team stuff – building the platform, running it, evolving it, consulting for it, etc.
They basically use Azure, with some AWS it seems:
~7:30 figuring this out all on your own can be very time consuming – maybe a couple years of learning, PoC’ing, [vendor negotiations], etc. We needed to do it in one. We started with the CNCF reference diagram.
[I didn’t pay attention closely enough much beyond to take good notes.]
The IT outcomes of Kubernetes are clear: 95% of businesses report clear benefits from adopting Kubernetes, with more efficient resource utilization and shorter software development cycles amongst the top benefits cited. The benefits don’t stop with the IT team, though. In an era where IT mostly determines competition and growth, the more agile the technology at the heart of a business, the greater the agility of the business overall.So, the business case for Kubernetes is clear. To those of us in IT at least.It makes sense that empowering development teams to do more in less time has clear benefits for businesses on paper. But given the inherent complexity of Kubernetes, the way in which these benefits actually manifest may not be so clear for those outside the IT department, particularly in the early stages of implementing the technology.Here, we look at why the tangible outcomes Kubernetes can provide across a business are worth overcoming initial challenges it may present, and what it means in the context of global events many organisations have been faced with in 2020 so far.
The answer is that Anthos is not really a technology, but more of a brand, a wrapper around Google’s cloud crown jewels, Kubernetes (K8s).
In a nutshell, Anthos is the GKE (Google Kubernetes Engine) deployed on-premises in a certified configuration (via hardware suppliers such as Dell and HPE), with an agent installed that maintains an encrypted connection to Google Cloud Platform (GCP). That agent lets you manage your Anthos cluster and its workloads from the GCP console, deploying and scaling applications. Anthos relies on good connectivity to GCP – for example, using Google Cloud Interconnect.
Could every element of an enterprise data center’s infrastructure — not just those newfangled containers, but virtual machines, “big data” platforms, and machine learning frameworks — all eventually become orchestrated by Kubernetes, a product originally born out of Google’s need to make order out of chaos?
“We need to think about three things with Pivotal now that it is part of VMware: a common substrate (Kubernetes), the ability to manage it, and a build overlay. The cf push experience is important, making the experience better for developers.” —Craig McLuckie, VMware
“We’re going to own the Kubernetes stack,” Gelsinger said at the Deutsche Bank Conference. “We’re not going to be relying on third-party code. It’s all going to be an integrated solution stack to execute on that Kubernetes.”
“Do we assess the competitive environment? Well, of course, we do,” Gelsinger said. “So, IBM spent $34 billion doing this. I spent $2.8 billion [on Pivotal], plus add Heptio. So, I spent less than $3 billion and I think I have better assets.”
“It’s optimized for cloud native applications – those that follow the patterns that are in my book for example. That represents only a subset of the applications that our enterprise customers need to address. Our 2020 strategy is to broaden the definition of our platform. To be more than just Cloud Foundry, but to broaden it to a larger range of use cases. To broaden it to a larger market.”
“The urgency was more around understanding the long term vision than an immediate need,” said Andrews. “We’re still very early. Everybody is talking about K8s all the time, but if you look at who is actually using it in production, the list is much shorter. Our technology stack works incredibly well, we have customers with over 100,000 containers working on the current platform. If we forecast out 3 to 5 years in the future though, it seems clear that K8s is going to be a de facto component in the architecture.”
With VMware Tanzu Mission Control, we are providing customers with a powerful, API driven platform that allows operators to apply policy to individual clusters or groups of clusters, establishing guardrails and freeing developers to work within those boundaries.
The company introduced VMware Tanzu, a marketing name for a portfolio of products and services, existing and new, that will help enterprises build modern applications, run Kubernetes with consistency across environments, and manage all their Kubernetes clusters from a single control point. It will encompass aspects of its recent purchase of Bitnami, a library of packaged installers for web applications and development stacks, and the planned acquisition of Pivotal, which offers application development tools, data management products, and analytics intelligence platforms.
Also, from Gartner analyst Paul Delory:
“Kubernetes is too complex for the average IT shop to build and operate effectively. We’ve known this for a while,” he said. “Because of this, the public cloud providers have all created their own managed K8S offerings. But these are cloud-specific, and not interoperable.
“So now IT shops have silos of K8S infrastructure living in different clouds. Someone has to be the one who can manage all this infrastructure, across clouds, and make it work together. VMware says they’re the one to do it. I am cautiously optimistic.”
A swag at how many new apps will be created to run on kubernetes cloud stuff. I assume this is actually existing, modernized apps and net-new ones despite the wording:
VMware says that from 2018 to 2023 – with new tools/platforms, more developers, agile methods, and lots of code reuse – 500 million new logical apps will be created serving the needs of many application types and spanning all types of environments.
“Kubernetes is a way of bringing a control metaphor to modern IT processes. You provide an expression of what you want to have happen, and then Kubernetes takes that and interprets it and drives the world into that desired state,” McLuckie explained.
The Tanzu portfolio also includes Project Galleon, which harnesses the packaging technology of VMware’s recent acquisition of Bitnami, to provide developers with an easy way to assemble software stacks. It will include a Platform as a Service development platform on its pending purchase of Pivotal. It also includes VMware Tanzu Mission Control, which will provide administrators with an overview of all Kubernetes clusters.
The platform also added an integration with VMware’s container orchestrator, Enterprise PKS, which means cloud providers can offer containers-as-a-service. And at VMworld the vendor will showcase a technology preview of vCloud Director integration with Bitnami Community.
VMware bought Bitnami in May. It provides application packaging targeted at container and Kubernetes environments. The Bitnami Community houses one of the largest catalogs of click-to-deploy applications and development stacks. Combining this with and Enterprise PKS will allow VMware Cloud Providers to “provide a cloud that’s developer ready, and offer both VM-based workloads and container-based workloads from the same platform,” Bhardwaj said
Anthos applications are deployed in software containers, which are used to host the individual components of each app and make them easier to work with. The main benefit is that developers get to use a single set of tools to build and deploy their apps, and push through updates as necessary, no matter what infrastructure those apps are hosted on. Kubernetes makes it easier to manage large clusters of containerized apps.
Sure you can do a lot of things with Kubernetes. It’s great, but Cloud Foundry is designed to make “Happy developers,” as Comcast open-source senior director Nithya Ruff put it at the Cloud Foundry Summit.
Cloud Foundry’s audience, as Karl Isenberg, one of its developers, explained on StackOverflow, is “enterprise application devs who want to deploy 12-factor stateless apps using Heroku-style buildpacks.”
“There are a million solutions out there to your technical problems, but what we wanted was to solve the people and process problems,”
“It depends on Pivotal. If they add a common pattern in the future for deployment with Istio and Envoy through a cluster and platform-agnostic service mesh, then, yes, we will combine them,” said another senior engineer at the carrier.
“A lot of work needs to be done for that but it’s evolving quickly,” Childers said of interoperability tests using Eirini as a bridge between Diego and Kubernetes. He did add that the evolution from Diego to Eirini, if it does occur, will be similar to how Cloud Foundry moved from its DEA architecture system to its Diego architecture system. That involved Diego having to show functional parity to DEA and the necessary production readiness for vendors and organizations to feel comfortable using Diego in place of DEA.