CloudNativeCon EU 2026 in Amsterdam brought together the CNCF community for three days of talks on Kubernetes, observability, service meshes, and platform engineering. UUID v7 appeared in multiple sessions as a cross-cutting concern — from trace IDs in service meshes to resource identifiers in Terraform modules. See UUID v7 in Distributed Systems for the broader context.
Session: UUID v7 as Kubernetes correlation IDs
The observability track session covered injecting UUID v7 at the ingress layer and propagating through the call graph:
# Kubernetes — inject correlation ID via Istio EnvoyFilter
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
name: uuid-correlation-id
spec:
configPatches:
- applyTo: HTTP_FILTER
match:
context: GATEWAY
patch:
operation: INSERT_BEFORE
value:
name: envoy.filters.http.lua
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.http.lua.v3.LuaPerRoute
inline_code: |
function envoy_on_request(request_handle)
if not request_handle:headers():get("x-correlation-id") then
-- Generate UUID v7 equivalent via timestamp + random
local ts = math.floor(os.time() * 1000)
request_handle:headers():add("x-correlation-id",
string.format("%012x-0000-7000-8000-000000000000", ts))
end
end
See UUID in Kubernetes and UUID v7 in Microservices.
Session: Kafka UUID v7 message keys
import { Kafka } from 'kafkajs';
import { v7 as uuidv7 } from 'uuid';
const kafka = new Kafka({ brokers: [process.env.KAFKA_BROKER!] });
const producer = kafka.producer();
// UUID v7 as message key — same entity = same partition, chronological order
async function publishEvent(entityId: string, payload: object) {
const messageId = uuidv7(); // unique per message, sortable
await producer.send({
topic: 'entity-events',
messages: [{
key: entityId, // routes to partition
value: JSON.stringify(payload),
headers: {
'message-id': messageId,
'x-correlation-id': messageId,
},
}],
});
}
// Time-range replay — consume from a specific timestamp
function uuidV7LowerBound(ms: number): string {
const hex = ms.toString(16).padStart(12, '0');
return `${hex.slice(0,8)}-${hex.slice(8,12)}-7000-8000-000000000000`;
}
See UUID v7 in Kafka Event Streaming.
Session: Terraform resource IDs
# Terraform — UUID v7 for application resource IDs
# (Terraform manages infrastructure; application IDs come from the app layer)
resource "aws_lambda_function" "order_processor" {
function_name = "order-processor"
environment {
variables = {
# Stable deployment ID — UUID v7 for this deployment
DEPLOYMENT_ID = "018fbe3a-4c5d-7b12-8abc-0123456789ab"
}
}
}
# Using Terraform's random_uuid resource for infrastructure IDs
resource "random_uuid" "workspace_id" {}
output "workspace_id" {
value = random_uuid.workspace_id.result
}
See UUID in Terraform Infrastructure for the full Terraform pattern.
Further reading
- UUID in Kubernetes
- UUID v7 in Kafka Event Streaming
- UUID v7 in Microservices — trace IDs
- UUID v7 in Distributed Systems
- UUID in Terraform Infrastructure
External references
Frequently asked questions
How is UUID v7 used in Kubernetes workloads?
Kubernetes assigns its own resource UIDs (UUID v4 by default). Application workloads running on Kubernetes use UUID v7 for application-level entity IDs — database primary keys, message IDs, trace correlation IDs. UUID v7 is passed to pods via environment variables or Kubernetes Secrets. The correlation ID pattern (inject UUID v7 at the ingress, propagate via HTTP headers) was a key topic at the conference. See UUID in Kubernetes.
Can UUID v7 be used as a Kafka message key?
Yes — Kafka message keys are arbitrary byte strings. Using UUID v7 as the key means messages for the same entity (same UUID prefix pattern) can be routed to the same partition while preserving event ordering within a partition. The timestamp prefix also enables time-range replays: consume only messages with keys greater than a given UUID v7 lower bound. See UUID v7 in Kafka Event Streaming.