We are very pleased to announce that we have received Federal Information Processing Standards (FIPS) Validation (CMVP Cert #3702) for the D2iQ Kubernetes Platform (DKP). With FIPS validation, U.S. public sector organizations can accelerate adoption of the D2iQ Kubernetes Platform to more quickly and securely build and deploy cloud native applications and services.

Innovation. Scale. Power. These are just a few of the words used to describe the explosive impact that Kubernetes is having on the organizations leveraging it for their innovation efforts. Kubernetes gives organizations the ability to run Kubernetes clusters at scale across different cloud infrastructures and distributions. But as the number of clusters and workloads grow, it can be increasingly difficult to manage and create consistency across your organization’s digital footprint.

The problem with a majority of governance models is that they aren’t continuous. As development teams adopt cloud native technologies and evolve to more agile methods, such as continuous flow and continuous iteration, they are up against decades of policy that assume an older model and don’t fit into a month-long sprint. While governance models need to be restructured, if they’re too restrictive, it can discourage developers and prevent innovation.

As various teams within your organization are discovering new ways to leverage Kubernetes, they’re adopting a growing number of clusters to support their project efforts. Unfortunately, this is where many of the challenges begin. While managing one Kubernetes cluster is not trivial, trying to manage multiple Kubernetes clusters across multiple environments becomes exponentially more difficult.

Businesses of all shapes and sizes are taking advantage of the hundreds of technology services that the cloud native landscape offers. Every few months, new open source projects, databases, and developer tools are coming out, and it’s empowering innovation across enterprises like never before.

Recently we hit the infamous kmem bug in our internal Production Konvoy Cluster. We discovered that we were having this issue after users began reporting a particular CI Job was failing intermittently throughout the Cluster with the following error: From the Pod Logs: From the Kernel Logs.