Tanzu Valkey support

Tanzu Valkey Support for Broadcom-Entitled Valkey on Kubernetes and VMs

Last reviewed by Tyler Eastridge

AceMQ provides 24/7 support for VMware Tanzu for Valkey, the Broadcom-built Valkey on VMs, Kubernetes and Tanzu Platform. Most calls start with one of three problems: latency spikes that line up with the save schedule, writes rejected with an out-of-memory error, or replicas that keep falling back to a full resync.

AceMQ is Broadcom's 2025 Tanzu Partner of the Year, a Leading Broadcom Tanzu partner and a Leading Global Services Partner. Valkey inherits Redis's operational surface exactly — fork stalls during RDB snapshots, transparent huge pages wrecking tail latency, evictions that never fire, replicas resyncing in a loop. Every ticket reaches a named senior engineer who knows your topology.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Valkey consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Tanzu Valkey problems we fix every week, and what an engineer checks first

Seven faults seen on Tanzu for Valkey, with the INFO section, command or operator event an engineer checks first.

Common Valkey production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Latency spikes of hundreds of milliseconds at save timeINFO persistence for latest_fork_usec and rdb_last_bgsave_status, plus LATENCY DOCTOR. A slow fork on a large heap stalls the main threadMove saves to a replica, schedule them, or reduce heap per node
Writes rejected with an out-of-memory error while eviction should runINFO memory: maxmemory, maxmemory-policy and used_memory against the container or host limit. The noeviction policy rejects writesSet an eviction policy fit for the data; leave headroom for fork copy-on-write and replication buffers
Replicas disconnect and fall back to a full resyncINFO replication and the log: repl-backlog-size against write volume, and client-output-buffer-limit for replicasEnlarge the backlog and output buffer so a short disconnect resumes with a partial sync
Resharding stuck with slots in migrating or importing stateCLUSTER NODES and CLUSTER SLOTS for slot states across nodesComplete or clear the stuck slot with valkey-cli --cluster fix, after checking both nodes agree
One node at 100% CPU on modest operations per secondSLOWLOG GET and INFO commandstats, then large keys and KEYS or big-range commandsReplace the command, split the key, add a read replica
Reported memory far above stored key sizesINFO memory fragmentation ratio and MEMORY DOCTOR, then client buffersActive defragmentation settings, or a controlled restart on a replica first
Operator-managed pod restarts and clients lose the primaryOperator and pod events, readiness probes, and client topology refresh settingsFix probes and resource limits; make clients re-resolve after failover

A P1 closes with a written root cause that names the setting, key pattern or pod event involved and the fix we applied.

Writes failing with out-of-memory errors on a production Valkey? Request a quote and an engineer responds in an hour.

Contact Us

Deployment coverage

Which Tanzu Valkey deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat Broadcom coversExcluded
Tanzu for Valkey on VMs (7.2.x and 8.0.x lines)24/7 incident response, RCA on P1s, persistence, memory and replication tuningBroadcom builds, ships and supports Tanzu for Valkey for entitled customers (advisories on support.broadcom.com)Patched Tanzu builds
Tanzu for Valkey on Kubernetes (operator)Operator behaviour as it affects Valkey: failover, storage, resource limits, upgradesBroadcom supports the operator and its releasesCluster control plane
Tanzu for Valkey on Tanzu PlatformValkey layer: memory, latency, clientsBroadcom supports the platform integrationPlatform faults
Cluster mode and replicationSlot balance, failover, resharding, backlog sizingProduct defectsNetwork faults
Redis-to-Valkey migrationPlan and rehearsal; see the Redis to Valkey migration pageNot coveredApplication rewrites

Better together

Broadcom subscription plus AceMQ engineers: how Tanzu Valkey support fits together

Broadcom provides Tanzu for Valkey to entitled customers and publishes release advisories for it. AceMQ adds 24/7 engineers for the Valkey behaviour around those builds, and the same people support open-source Valkey and Redis.

Broadcom subscriptionAceMQ engineers alongside it
What it coversThe Broadcom build, its operator and its releasesThe Valkey estate: latency, memory, replication, clients
Hours and responsePer the terms of your subscription24/7 across Americas, EMEA and APAC; response targets from 15 minutes, by plan
Open-source Valkey and RedisNot coveredCovered
Root cause analysisPer Broadcom's processWritten root cause analysis on every P1
Product defectsShips fixed builds and handles product defectsWe diagnose, gather the evidence and work the escalation with you
PriceSet by the Broadcom subscription$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

If you need the commercial features, the entitlement or the fixed builds, you buy them from Broadcom. If you also want senior engineers on call across time zones, that is a separate contract that sits beside it. Many estates do both, and AceMQ is a Leading Global Services Partner for Broadcom.

Something changed?

Renewal under Broadcom's model? Start here

Each guide says what changed, who it affects and what to decide first.

What's Included

Everything in your Valkey support contract

The Tanzu build, its operator and the Valkey instances underneath are handled together, from persistence settings to slot migration.

  • 01

    Emergency Incident Response

    Primary down, writes rejected, or a cluster stuck mid-reshard on a Tanzu build. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge, 24/7, with access to diagnose rather than a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the persistence, eviction, probe or host change that stops it recurring.

  • 03

    Latency and Memory Tuning

    Fork and persistence strategy, eviction policy against real TTL coverage, fragmentation settings, hot key detection and client pooling.

  • 04

    Operator and Upgrade Checks

    Tanzu patch notes, operator versions and Valkey versions move on different clocks. We build the compatibility check for an upgrade, rehearse it and keep a rollback at each step.

  • 05

    Cluster and Failover Operations

    Slot balance, failover, resharding and replica placement, with failover tested while clients are connected.

  • 06

    Entitlement Questions

    We help you read your Broadcom entitlement against what you run, and work the product escalation with you. We do not sell licences.

Why AceMQ

Why teams add AceMQ to a Tanzu Valkey deployment

  • The Valkey Behind the Tanzu Build

    Broadcom supports its build for entitled customers. Latency, memory, replication and client behaviour are where most incidents start, and that is the layer our engineers work in, with the same people covering open-source Valkey and Redis.

  • No Tier-1 Triage Layer

    You reach a senior engineer directly by phone, email or Slack. Nobody collects details to pass along while writes are failing.

  • Host-Level, Not Just Config-Level

    Many Valkey latency problems are host problems: transparent huge pages, overcommit, swap or storage. We diagnose down to the host.

  • Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries, so a 3am eviction storm reaches someone who is already at work.

  • Proactive, Not Just Reactive

    Health checks cover memory, fragmentation, replication backlog, persistence timing and slot health, and shared intelligence flows across our support base when a version-specific bug appears.

Where Tanzu Valkey runs, and where we support it

Valkey on VMs, on Kubernetes through the operator, and on Tanzu Platform, in standalone, replicated and cluster layouts.

  • Tanzu for Valkey on Kubernetes (operator)
  • Tanzu for Valkey on VMs
  • Tanzu for Valkey on Tanzu Platform
  • VMware vSphere and Tanzu
  • Kubernetes and OpenShift
  • Bare metal and on-premises
  • Air-gapped / no outbound access
  • Valkey Cluster mode
  • Sentinel-managed deployments
  • Redis estates in migration

Version coverage

Versions we support

Versions we support
LineNotes (Broadcom advisories, searched 17 Nov 2026)AceMQ coverage
Tanzu for Valkey 8.x8.0.5 to 8.0.7 and 8.1.3 advisories found24/7 support
Tanzu for Valkey 7.2.x7.2.9 to 7.2.11 advisories found24/7 support
Tanzu for Valkey on Kubernetes (operator)3.5.0 advisory dated 4 Sep 2026; 3.4.2 dated 3 Aug 202624/7 support
Tanzu for Valkey on Tanzu Platform10.2.2 advisory, March 202624/7 support

Broadcom's own support windows per line are on its portal and are not restated here. Advisories show several releases driven by upstream Valkey vulnerabilities.

In practice

What is specific to Tanzu Valkey

Tanzu for Valkey is Broadcom's packaging of the open-source Valkey project. Broadcom's advisories show a first general release in March 2025 alongside Valkey 8.0.2 and 7.2.8, then separate release lines for the VM build, a Kubernetes operator build and a Tanzu Platform build.

The practical result: patch notes, operator versions and Valkey versions move on different clocks, so an upgrade needs a compatibility check across all three. AceMQ builds that check for you, rehearses it and keeps a rollback at each step.

Running open-source Valkey, ElastiCache or Memorystore instead? See Valkey support.

Escalation Path

Your first hour of a Valkey outage

The engineer on the line already thinks in fork times, backlog sizes and slot states, so we skip the generic intake questions.

  1. From 15 min (by plan)first responseEmergencyProduction down: the primary is lost and clients cannot find a new one, the operator keeps restarting pods, or writes are rejected across the board
  2. 1 hourfirst responseCriticalSevere impact: replicas looping through full resyncs, save-time stalls of hundreds of milliseconds, slots stuck migrating during a reshard
  3. 4 hoursfirst responseHighA node pinned at 100% CPU from KEYS or large ranges, memory far above key sizes, eviction not engaging
  4. Next Dayfirst responseStandardQuestions on maxmemory-policy, repl-backlog-size, persistence choices, client refresh settings and upgrade order

Writes rejected at peak traffic and a question about replica sizing do not share a response clock; your plan sets each one.

Want someone who knows your topology on the line before the next failover? Get a quote or message us.

Contact Us

Pricing

What does AceMQ Valkey support cost?

Support for Tanzu Valkey generally falls between $24,000 and $72,000 a year. The figure follows your topology (single node, replicated, cluster), the memory you hold, how you persist data and the response plan.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, with quote requests answered within 1 hour. Adding Redis, Memcached or other Tanzu data services to one contract earns a multi-technology discount.

Support In Practice

Cache problems we have worked through

Valkey support, migration and patching work from AceMQ. Each card links to the full write-up: the Valkey estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

  • Remediation

    Redis to Valkey Migration Under Memory Pressure

    Digital Collaboration Platform

    A production Redis cluster was crashing under memory growth traced to its full-text index rather than to the workload. AceMQ diagnosed the leak, stabilized the cluster, and mapped the Valkey migration path.

    ValkeyRedisKubernetes
  • Support

    Valkey Cluster Resharding Stuck Mid-Migration

    Regional Payments Processor

    A Valkey Cluster resharding ahead of a seasonal peak stalled with slots left in migrating and importing states. AceMQ resolved the slots on both nodes, finished the move in controlled batches and set up support for the next one.

    ValkeyKubernetesPrometheus
  • CVE Patching

    Valkey 7.2 Security Patching Without a Forced Upgrade

    Benefits Administration Provider

    A regulated provider could not move its on-premises Valkey 7.2 clusters for another year. AceMQ assessed each security advisory against its configuration and backported the fixes through OSSeva.

    ValkeyLinuxRedis Sentinel
  • Assessment

    Redis to Valkey Compatibility Assessment Across 41 Instances

    European Telecom Operator

    A telecom operator wanted to move its Redis estate to Valkey but did not know which instances could move cleanly. AceMQ assessed commands, scripts, modules and clients instance by instance and ordered the migration.

    ValkeyRedisKubernetes
  • Consulting

    Valkey 8 to 9 Upgrade Plan with a Replica-First Order

    Platform Engineering Team

    A typical consulting engagement for a team on Valkey 8.0 clusters: a written upgrade path to 9.x in replica-first order, rehearsed against the real command mix, with a rollback at each step.

    ValkeyKubernetesPrometheus
  • Consulting

    Valkey Session Cache Memory Sizing and Eviction Review

    Platform Engineering Team

    A typical consulting engagement for a Valkey session cache that refuses writes or evicts live sessions near its memory limit: a review of maxmemory, eviction policy, big keys and fork headroom.

    ValkeyLinuxPrometheus
All use cases

Support options

Four tiers of Valkey support.

AceMQ offers Tanzu Valkey support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for Valkey your team runs, proactive monitoring that catches fork, memory and failover problems first, managed Valkey on your own infrastructure, and fully managed Valkey on AceMQ infrastructure. Valkey 7.2 to 9.1 are covered in all four, with VMware Tanzu licensing for US customers.

  • Tier 1

    Valkey 24/7 Support & Incident Management

    Your platform team runs it, we take hard cases

    Best for: Teams comfortable operating Valkey day to day who want an expert for failovers, fork stalls and resharding that will not finish.

  • Tier 2

    Valkey 24/7 Support with Proactive Monitoring

    Regular reviews of memory, backlog and topology

    Best for: Services where a cache stall shows up as customer latency, and the settings behind it should be checked before it does.

  • Tier 3

    Managed Valkey on Your Infrastructure

    We operate Valkey and its operator on your hosts

    Best for: Organizations that must keep Tanzu Valkey in their own clusters but want specialists handling upgrades and failovers.

  • Tier 4

    Fully Managed Valkey on AceMQ Infrastructure

    We run the Valkey estate as a service

    Best for: Product teams that need a fast cache with failover and resharding handled, without staffing cache operations themselves.

FAQ

Valkey support questions

Still have questions about Valkey? Email an Expert

Who provides enterprise support for Tanzu Valkey?

Broadcom supports Tanzu for Valkey for entitled customers. AceMQ provides independent 24/7 support for it and for open-source Valkey and Redis, with response targets from 15 minutes, by plan.

Is Valkey experience really the same as Redis experience?

Mostly: Valkey continues from Redis 7.2 and the commands and persistence behaviour are close. Where behaviour has diverged we say so.

Can you migrate us from Redis to Valkey without downtime?

Usually, with replication-based cutover and a client test. See our Redis to Valkey migration page.

Why do latency spikes line up with saves?

Saving forks the process, and on a large heap the fork stalls the main thread. Compare latest_fork_usec in INFO persistence with the spike times, then consider the save schedule or replica-based saves.

What does 24/7 Tanzu Valkey support include?

A named engineer on live incidents at any hour, response from 15 minutes by plan. In a Sev 1 where the primary is lost and clients cannot find the new one, we check operator events and topology refresh, then write the root cause. P2 is 1 hour, P3 4 hours, P4 next business day.

What is the difference between this page and your Valkey support page?

This page is for Broadcom's Tanzu builds and operator; the Valkey support page covers open-source and cloud Valkey.

Can you help with Broadcom licensing?

Yes. We check your entitlement against the Valkey instances and Tanzu data services in use. We do not sell licences.

Can we hire you for one Valkey problem rather than a full year?

Yes. A latency investigation, a failover test, a cluster resharding or an upgrade plan across the build, operator and Valkey can be done as a single scoped job. Many customers move to annual 24/7 cover afterward with the same engineer.

How much does Tanzu Valkey support cost, and why?

Most contracts sit between $24,000 and $72,000 a year (USD). We price by topology, total memory, persistence mode, the number of production instances and the response plan. Tell us how many shards and replicas you run and a quote arrives within 1 hour.

Let's talk

Running Tanzu for Valkey in production?

Send the Valkey version, the operator version and your topology. We reply within 1 hour.

A senior Valkey engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a Valkey Architect