Cloudflare KV Namespace

Deploys a Workers KV namespace on Cloudflare. Workers KV is a globally distributed, low-latency key-value store designed for read-heavy workloads at the edge. This component creates a single KV namespace that can be bound to Cloudflare Workers for storing configuration, session data, feature flags, or any other data your edge logic needs.

What Gets Created

When you deploy a CloudflareKvNamespace resource, OpenMCF provisions:

• Workers KV Namespace — a cloudflare_workers_kv_namespace resource with the title set to the configured namespaceName

The namespace ID is exported as a stack output so that other components (such as CloudflareWorker) can reference it at deploy time.

Prerequisites

• Cloudflare credentials configured via environment variables or OpenMCF provider config
• A Cloudflare account with Workers KV enabled on the plan
• Appropriate permissions — the API token must have Workers KV Storage:Edit access

Quick Start

Create a file kv-namespace.yaml:

apiVersion: cloudflare.openmcf.org/v1
kind: CloudflareKvNamespace
metadata:
  name: my-kv
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.CloudflareKvNamespace.my-kv
spec:
  namespaceName: my-kv-store

Deploy:

openmcf apply -f kv-namespace.yaml

This creates a KV namespace titled my-kv-store in your Cloudflare account. Bind it to a Worker using the namespace ID from status.outputs.namespaceId.

Configuration Reference

Required Fields

Optional Fields

Examples

Basic KV Namespace

A minimal KV namespace suitable for development or testing:

apiVersion: cloudflare.openmcf.org/v1
kind: CloudflareKvNamespace
metadata:
  name: dev-cache
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.CloudflareKvNamespace.dev-cache
spec:
  namespaceName: dev-cache

Session Store with TTL Hint

A KV namespace intended for session data, with the spec recording a 1-hour TTL intent:

apiVersion: cloudflare.openmcf.org/v1
kind: CloudflareKvNamespace
metadata:
  name: session-store
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.CloudflareKvNamespace.session-store
spec:
  namespaceName: prod-session-store
  ttlSeconds: 3600
  description: "Session data for authenticated users"

Feature Flags Namespace

A KV namespace dedicated to feature flag storage, referenced by multiple Workers:

apiVersion: cloudflare.openmcf.org/v1
kind: CloudflareKvNamespace
metadata:
  name: feature-flags
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.CloudflareKvNamespace.feature-flags
spec:
  namespaceName: feature-flags-prod
  description: "Global feature flags consumed by edge Workers"

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• CloudflareWorker — Workers consume KV namespaces via bindings; use the namespaceId output to wire a KV store to your Worker
• CloudflareR2Bucket — object storage for larger or binary data, complementary to KV for small-value, read-heavy access patterns
• CloudflareD1Database — relational SQL storage at the edge; use when you need structured queries rather than simple key-value lookups
• CloudflareDnsZone — manages DNS zones that front the Workers consuming this KV namespace