VM Workload Isolation in Kubernetes Pods via Serial Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cluster environments using namespace-based isolation in Kubernetes pods lack sufficient security as containers within the same pod can communicate directly, posing a risk if one container is malicious or erroneous, potentially harming others or the host.

Innovation Solution

Implementing a network structure that isolates virtual machine (VM) workloads within pods by converting data packets into a serial format, routing them through a router on the host computer, and using destination network address translation (DNAT) logic to ensure indirect communication between containers, thereby preventing direct interaction and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If namespace-based isolation is used in Kubernetes pods, then start-up time and efficiency are improved, but security isolation between containers within a pod deteriorates

Engineering Contradiction:
Improvestart-up timeVSAvoidsecurity isolation
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system segments containers into different isolation layers: namespace-based logical grouping for efficiency, and VM-based hardware-level isolation for security. Each container is assigned to a specific VM within the pod, creating hierarchical segmentation that resolves the contradiction between fast namespace-based operations and secure isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A router is introduced as an intermediary component that mediates all communication between containers within a pod. The router enforces isolation policies and controls traffic flow, preventing direct container-to-container communication while maintaining namespace-based operational efficiency. This intermediary layer resolves the security-efficiency contradiction by adding controlled mediation without eliminating the efficient namespace structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If containers within a pod can communicate directly, then communication efficiency is improved, but security risk increases due to potential malicious or erroneous code

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The router serves as a security intermediary that all container communications must pass through. It implements security policies, filters traffic, and prevents direct container interaction, thereby eliminating security risks while maintaining efficient communication through the mediated path. The router acts as a controlled gateway that preserves productivity without exposing systems to harmful factors.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements a flexible isolation shell at the VM level that encapsulates each container. This thin film of virtualization provides security boundaries while allowing controlled communication through the router. The shell maintains communication efficiency by enabling structured traffic flow while blocking unauthorized direct access between containers.

Inventive Principle:
Principle #30Flexible shells and thin films

3Reliability

If VM-based isolation is implemented for each container, then security isolation is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity isolationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses universal VM infrastructure that can host multiple containers within a single pod. Each VM is configured with multi-functional capabilities to handle different container workloads, reducing the need for separate specialized systems. This universality maintains strong security isolation while managing complexity through standardized, multi-purpose virtualized environments.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The architecture implements nested isolation where containers are nested within VMs, which are nested within pods, all managed by the Kubernetes cluster. This nested structure provides multiple layers of security isolation without requiring each layer to be fully independent, thereby managing complexity through hierarchical organization. The nested doll approach allows security isolation at the VM level while maintaining pod-level container management efficiency.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12099863B2Isolating virtual machine workloads within pods in a cluster environment
Publication Date: 2024.09.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12099863B2 patent drawing
  • US12099863B2 patent drawing
  • US12099863B2 patent drawing

AI summary

Aspects include providing isolation between a plurality of containers in a pod that are each executing on a different virtual machine (VM) on a host computer. Providing the isolation includes converting a data packet into a serial format for communicating with the host computer. The converted data packet is sent to a router executing on the host computer. The router determines a destination container in the plurality of containers based at least in part on content of the converted data packet and routes the converted data packet to the destination container.