Category: Business, Security, Kubernetes, Infrastructure, encryption, automation

Odds are that your organization is well on its way to being a hybrid cloud user.

Rather, it means that deployment architectures are complex, evolve quickly and that it makes no sense to decide cloud architecture in a “one-and-done” fashion.

Early experiments by users show that this approach quickly reduces TCO for private cloud operations.

The bottom-line requirement for using Kubernetes as “the infrastructure” is that you need to be able to deploy, observe and manage the lifecycle of one consistent Kubernetes cluster model anywhere.

This implies that someone (hopefully not you) is enabling this functionality and enabling Kubernetes to actively manage diverse underlying infrastructures gracefully.

Related Articles