Adaptability-as-a-Service with Kubernetes

April 10, 2018 Cornelia Davis

How running your apps on Kubernetes makes them more tolerant to change.

In the IT business, we live in an environment where everything is changing. Business requirements are changing. User demands are constantly in flux and always evolving. And our infrastructure is also continually changing. Frankly, the infrastructure has always been in a constant state of change, but in the past we pretended that we could get it to a point of stability — that we could reach a state of “done.” Once we finished setting up that totally stable infrastructure, then we could run everything on top with no problems, right?

IT is perpetually in firefighting mode because it treats change as the exception, not the rule. Yet, change is the only constant in our world.

The increased use of containers in recent years has come largely out of the value that the container image brought — having a deployable artifact (the docker image) that bundled together all dependencies, from the operating system through middleware and the application components, enabled significant advancements in development and operational (DevOps) efficiencies. And the speed with which containers could be launched helped to expand and refine practices around infrastructure as code and immutable infrastructure. But containers alone do not address the need for constant adaptation.

Just as with the infrastructure virtualization that was ushered in by VMWare twenty years ago and delivered as a service starting with AWS, the introduction and early adoption of containers has left so much of the way IT works largely unchanged. True, the use of automation has increased the very infrastructure as code that I mentioned a moment ago, but it has mostly resulted in the automation of existing practices — a script to install the docker runtime on three hosts, another to “docker run” three different microservice images, and yet another to adjust firewall rules to allow traffic through. This automation still assumes a level of stability; after running the scripts we are “done” and things will just keep humming along. But when, for example, two of the docker hosts are suddenly unavailable, the team is once again in firefighting mode.

Enter container orchestration. The most popular container orchestration system in the industry today is Kubernetes, and with good reason. What makes Kubernetes and other similar systems, like Pivotal Cloud Foundry®, really shine is that the system operates in a mode that anticipates constant change — in fact, if I were watching a sci-fi movie I’d almost say it likes it.

The DNA of Adapability

The Kubernetes model is so effective because it allows a user to say “here’s my desired state. I want 2 instances of my user-facing web page, 3 instances of my catalog service and 10 instances of my shopping cart service” and Kubernetes just makes it so. It is a declarative model for defining complex systems. Kubernetes constantly monitors the actual state of the system and any time it differs from the desired state it will remediate. So, if we lose the (docker) host on which some of the instances are running, Kubernetes will automatically relaunch any necessary services on the remaining hosts so that the desired state is once again realized. Kubernetes has change-tolerance built into its DNA.

Kubernetes can be adapted to host and manage a virtually endless set of different types of workloads.

Another thing that taxes an IT team is the variability they have in their infrastructure. There are different server and storage platforms and an arguably even more varied set of networking solutions. And increasingly, enterprises are going hybrid, leveraging a combination of on premise and public cloud infrastructures. This means that not only must IT teams become experts in the management interfaces for many different clouds, the scripts they are writing to automate the myriad of different tasks must be written and maintained for each different infrastructure. Kubernetes addresses this by providing abstractions over the top of the varied infrastructure assets, allowing kubernetes consumers to leverage that infrastructure through common entities such as workloads (pods and replica sets), networks and network policies (NetworkPolicy) and storage (Storage Classes, Persistent Volume Claims). Kubernetes is designed to adapt to the infrastructure.

Finally, and perhaps the thing that gets me most excited about Kubernetes, is it’s extensibility. Out of the box Kubernetes already delivers a whole host of resource types — pods, storage classes, roles and so much more — and functionality to lifecycle manage those resources — replica sets, daemon sets, stateful sets and more, but particularly when it comes to stateful workloads like a database, cache, or indexing services, each one has unique needs. The way that Mongo DB protects data that it stores is quite different from the way that MySQL does, for example. Kubernetes allows for custom resource definitions (CRDs) and associated behaviors (one of the most popular means for this is via operator) to be added, effectively extending the reach of the platform. That is, Kubernetes can be adapted to host and manage a virtually endless set of different types of workloads.

When you look at the abstractions that Kubernetes provides it’s easy to think of it as a new API for infrastructure — its base primitives are compute, storage, and network, just as with server virtualization. It is its tolerance for change that sets it apart. That same change tolerance, by the way, is what sets Kubernetes apart from Docker alone which is fundamentally focused on running images, but does nothing for lifecycle management.

Who is Kubernetes for?

Just as with Docker and server virtualization before that, initially Kubernetes has captured the mindshare of the developer. Particularly now that those developers are increasingly responsible for keeping their software running well in production, having an intelligent, autonomous system that helps them with those operational tasks is hugely valuable to them. App operations involves not only the day 1 task of deployment but also maintenance in the face of infrastructure changes, security vulnerabilities, and more. Kubernetes aids in all of that.

Just as enterprise IT provides centralized, secure, compliant, and resilient virtualized infrastructure environments, the time has come for providing secure, compliant, and resilient container platforms.

But Kubernetes has sufficient flexibility to run software that an organization is not actively developing, such as apps that are strictly running in maintenance mode, or software provided by an ISV. Today these applications are largely running on virtualized infrastructure with expectations of relative stability. Hosting these applications on Kubernetes can immediately add a level of resilience and security.

And finally, the train has left the station. It’s rare these days that I speak to an enterprise that does not have some, sometimes substantial, presence of container-centric efforts going on. Often it has grown out of a development group that has built its practices around containers. They’re building docker images for their apps but, because the enterprise does not already have a production platform that can run those images, the same app teams are managing the container platform. Just as enterprise IT provides centralized, secure, compliant, and resilient virtualized infrastructure environments, the time has come for providing secure, compliant, and resilient container platforms. Kubernetes has emerged as a clear market leader in that space.

As Kubernetes Becomes Mission Critical

With the capabilities that it brings for running and managing mission-critical workloads, Kubernetes itself must be equally resilient to change. If a security vulnerability is found that requires Kubernetes be upgraded, it must be patched quickly and with zero downtime for the workloads it is hosting. If application capacity requirements suddenly spike, the Kubernetes capacity must be quickly expanded to meet the need. When the spike has passed, Kubernetes needs to be right-sized again to keep IT infrastructure costs in check.

These are exactly the challenges that Kubernetes is addressing for containerized workloads. The key is to use the same principles and techniques that Kubernetes uses for workloads to manage Kubernetes itself. We need managed Kubernetes and this is precisely what Pivotal Container Service (PKS) does.

But that’s another story for another time.

Change is the only constant, so individuals, institutions, and businesses must be Built to Adapt. At Pivotal, we believe change should be expected, embraced, and incorporated continuously through development and innovation, because good software is never finished.

 

Adaptability-as-a-Service with Kubernetes was originally published in Built to Adapt  on  Medium, where people are continuing the conversation by highlighting and responding to this story.

About the Author

Cornelia Davis

Cornelia Davis is Vice President of Technology for Pivotal.

More Content by Cornelia Davis
Previous
Developing a Custom Concourse Resource
Developing a Custom Concourse Resource

This post provides a quick look at how to create your own custom Concourse resource.

Next
Improve Security and Developer Productivity with Service Instance Sharing in PCF 2.1
Improve Security and Developer Productivity with Service Instance Sharing in PCF 2.1

PCF 2.1 introduces a new capability that enables multiple development teams working on separate microservic...

×

Subscribe to our Weekly Newsletter

!
Thank you!
Error - something went wrong!