Skip to main content

Warm Pool Fast Activation

~10x faster MCP server cold starts using warm pool technology. Activate containers in ~1.3s instead of 8-15s.

Overview

The warm pool system pre-provisions container pods that can be rapidly activated with MCP server images. This dramatically reduces cold start latency for on-demand MCP tool execution.

How It Works

Activation Flow

Timing Breakdown


Architecture

Components

Warm Pool DaemonSet

Warm pool pods are deployed as a Kubernetes DaemonSet:

Activation Service

The activation service runs inside each warm pod:

Configuration

Feature Flags

Enable warm pool via feature flags:

Helm Values

Configuration Options


Image Handling

Skopeo Integration

Images are downloaded using Skopeo for efficient layer handling:

Layer Extraction

ENTRYPOINT/CMD Parsing


Pool Management

Pod Selection

State Reconciliation

The state reconciler ensures pool health:

Security Considerations

Warm pool pods run with privileged: true for chroot capability.

Security Measures

Best Practices

  1. Limit pool access - Only MCP Manager can activate pods
  2. Image allowlist - Restrict which images can be activated
  3. Resource limits - Set CPU/memory limits on activation pods
  4. Audit logging - Log all activation requests
  5. Regular rotation - Periodically recycle warm pods

Monitoring

Metrics

Health Checks


Troubleshooting

Common Issues


Next Steps

MCP Integration

Configure MCP servers

Deployment

Deploy to Kubernetes