Microsoft recently reported two widespread cryptomining attacks targeting Kubeflow, a popular cloud-native platform for machine learning (ML) workloads on Kubernetes. Attackers targeted Kubeflow installations using either the Kubeflow central dashboard interface or Kubeflow Pipelines interface for scheduling crypto-mining workloads.
In order to run Kubernetes in production, you need more than just the base Kubernetes, but a variety of other necessary add-on services, such as monitoring, security, disaster recovery, and more. However, navigating the cloud-native ecosystem is complex and rapidly changing, making it difficult to build a robust production platform required to run mission critical business services.
Containerization has evolved from the early days of Linux control groups to out-of-the-box solutions offered by cloud providers. Market analysts expect a rise to more than 70% of global organizations using one or more containers by 2023, a huge uptick from less than 20% of them running containers for their applications in 2019.
In a relatively short amount of time, Kubernetes has evolved from an internal container orchestration tool at Google to the most important cloud-native technology across the world. Its rise in popularity has made Kubernetes the preferred way to build new software experiences and modernize existing applications at scale and across clouds. With Kubernetes, companies can host workloads running on a single cloud, as well as workloads across multiple clouds.
Without a strategy in place, it will introduce a handful of challenges. Platform teams will be unable to do the following: As you’re defining policies for multi-tenant AKS, EKS, or GKE clusters, consider these tips: To help you get started on the right track, we created this cheatsheet for multi-tenancy success.
Nobody wants to deal with annoying neighbors. Whether it’s the neighbor who always knows everyone’s business or the one who turns up their music late at night, both types of neighbors can have a negative impact on your living environment and daily life. Obnoxious neighbors aren't exclusive to just your physical living space, but in the public cloud where there are multiple Kubernetes clusters (EKS, AKS, or GKE) and multiple users (or tenants) with the need for cluster access.
To continuously innovate, many organizations are anchoring their infrastructure on container management solutions. The open source project Kubernetes is now the de facto standard for container management, and its popularity is growing in a number of ways. Here are some stats from a recent Cloud Native Computing Foundation (CNCF) survey.
It’s that time again: the latest versions of D2iQ Konvoy and D2iQ Kommander have just been made generally available and the D2iQ Kubernetes Platform (DKP) has some powerful new features. As noted with our last update, DKP is the leading independent Kubernetes platform for enterprise grade production at scale and Konvoy and Kommander are the reason why. You can learn more about Konvoy here, Kommander here, and our general approach here.
If your organization is adopting multiple Kubernetes clusters, chances are that multiple users or groups have access to these clusters on the same shared infrastructure. Kubernetes multi-tenancy aims to drive efficient use of infrastructure, while providing operators with robust isolation mechanisms between users, workloads, or teams. Running more applications on the same shared infrastructure means better utilization of resources and a reduction in overall operating costs.
We are seeing organizations struggle to deploy and manage their Kubernetes clusters due to the increasing level of oversight required and the current lack of attention during the planning phase. Day 2 operations can be a “sink or swim” time for these organizations. Without effective Day 2 operations, organizations will face challenges scaling their IT environment and will not be ready to handle new threats to security and availability.
