Skip to content

docs: Cloudflare Mesh container image documentation #32576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nikitacano merged 2 commits into from
Aug 7, 2026
Merged

docs: Cloudflare Mesh container image documentation #32576

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a1a4459
docs: add Cloudflare Mesh container image documentation and changelog
nikitacano Aug 6, 2026
bdeec90
fix: use dedicated warp_connector Terraform resources for Mesh nodes
nikitacano Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions src/content/changelog/mesh/2026-08-07-mesh-container-image.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: Container image for Cloudflare Mesh
description: Run a Cloudflare Mesh node as a Docker container for Docker Compose, Kubernetes, and CI/CD environments.
date: 2026-08-07
products:
- mesh
- cloudflare-one
---

import { DashButton } from "~/components";

[Cloudflare Mesh](/cloudflare-one/networks/connectors/cloudflare-mesh/) nodes can now run as Docker containers. The [`cloudflare/mesh`](https://hub.docker.com/r/cloudflare/mesh) image is available on Docker Hub for Docker Compose, Kubernetes, and any OCI-compatible runtime — no host-level package installation required.

The image supports `amd64` and `arm64` architectures and includes built-in [source NAT](/cloudflare-one/networks/connectors/cloudflare-mesh/containers/#source-nat) so return traffic routes correctly without VPC route table changes.

### Deployment patterns

- **Docker Compose** — add a `cloudflare-mesh` service to your `compose.yaml` and connect your entire stack to a private network.
- **Kubernetes StatefulSet** — deploy a standalone Mesh node with persistent registration state.
- **Kubernetes sidecar** — add the Mesh image as a sidecar container in a Pod to connect an application to Cloudflare without application changes.
- **CI/CD** — pull the image in a pipeline step, join the Mesh, run integration tests against private infrastructure, and tear down. The node disappears when the container exits.

For [high availability](/cloudflare-one/networks/connectors/cloudflare-mesh/high-availability/), run multiple replicas with the same Mesh node token. Cloudflare operates replicas in active-passive mode with automatic failover.

<DashButton url="/?to=/:account/mesh" />

For setup steps, runtime configuration, and deployment examples, refer to [Run Mesh in Docker / Kubernetes](/cloudflare-one/networks/connectors/cloudflare-mesh/containers/).
Loading