ScyllaDB University Live | Free Virtual Training Event
Learn more
ScyllaDB Documentation Logo Documentation
  • Deployments
    • Cloud
    • Server
  • Tools
    • ScyllaDB Manager
    • ScyllaDB Monitoring Stack
    • ScyllaDB Operator
  • Drivers
    • CQL Drivers
    • DynamoDB Drivers
    • Supported Driver Versions
  • Resources
    • ScyllaDB University
    • Community Forum
    • Tutorials
Install
Search Ask AI
ScyllaDB Docs ScyllaDB Operator Deploy ScyllaDB Set up networking IPv6 networking

IPv6 networking¶

IPv6 networking support enables you to run ScyllaDB clusters on IPv6 networks, with options for IPv6-only, IPv4-only, or dual-stack (both protocols) configurations.

Note

IPv6-only configurations are experimental. All other configurations are production-ready. See Production readiness for details.

Tutorials¶

Start here if you’re new to IPv6 networking in ScyllaDB:

  • Getting started with IPv6 networking - Your first IPv6-enabled cluster with step-by-step guidance

How-to guides¶

Practical guides for specific tasks:

  • Configure dual-stack networking - IPv4-first (recommended) and IPv6-first dual-stack

  • Configure IPv6-only - IPv6 single-stack (experimental)

  • Migrate clusters to IPv6 - Migrate existing clusters from IPv4 to IPv6

  • Troubleshoot IPv6 networking issues - Diagnose and resolve common problems

Reference¶

Technical specifications and API details:

  • IPv6 configuration reference - Complete API reference for IPv6 settings

Concepts¶

Deep explanations of how IPv6 networking works:

  • IPv6 networking concepts - Understand how IPv6 support works in ScyllaDB

Configuration examples¶

Quick examples for common scenarios:

Dual-stack (recommended for production):

network:
  ipFamilyPolicy: PreferDualStack
  ipFamilies:
    - IPv4  # ScyllaDB uses IPv4
    - IPv6  # Services also support IPv6
  dnsPolicy: ClusterFirst

IPv6-only (experimental):

network:
  ipFamilyPolicy: SingleStack
  ipFamilies:
    - IPv6
  dnsPolicy: ClusterFirst

IPv4-only (default):

network:
  ipFamilyPolicy: SingleStack
  ipFamilies:
    - IPv4

For complete examples, see the how-to guides.

Key concepts¶

IP family selection¶

The first IP family in network.ipFamilies determines which protocol ScyllaDB uses internally:

  • [IPv6] → ScyllaDB uses IPv6

  • [IPv4, IPv6] → ScyllaDB uses IPv4, services support both

  • [IPv6, IPv4] → ScyllaDB uses IPv6, services support both

Learn more in IPv6 networking concepts.

Dual-stack behavior¶

“Dual-stack” refers to Kubernetes services having both IPv4 and IPv6 addresses. ScyllaDB itself always runs on a single IP family (the first one configured).

This provides client flexibility while maintaining internal consistency.

DNS configuration¶

For IPv6, dnsPolicy: ClusterFirst is essential to ensure proper DNS resolution of IPv6 addresses.

Prerequisites¶

Before configuring IPv6:

  • Network: Cluster must have IPv6 networking configured

Feature status¶

Configuration

Status

Production Ready

Dual-stack (IPv4 + IPv6)

Stable

Yes

IPv6-only

Experimental

No

IPv4-only

Stable

Yes

For IPv6-only production support progress, see #3211.

Getting help¶

If you need assistance:

  1. Check documentation: Review the troubleshooting guide and concepts

  2. Search issues: Look for similar problems in GitHub issues

  3. Ask the community: Join ScyllaDB Slack

  4. Open an issue: Report bugs or request features on GitHub

Related documentation¶

  • Networking overview

  • Kubernetes IPv6 Documentation

Was this page helpful?

PREVIOUS
Configure external access
NEXT
Getting started with IPv6 networking
  • Create an issue
  • Edit this page

On this page

  • IPv6 networking
    • Tutorials
    • How-to guides
    • Reference
    • Concepts
    • Configuration examples
    • Key concepts
      • IP family selection
      • Dual-stack behavior
      • DNS configuration
    • Prerequisites
    • Feature status
    • Getting help
    • Related documentation
ScyllaDB Operator
Search Ask AI
  • v1.21
    • master
    • v1.21
    • v1.20
    • v1.19
    • v1.18
  • Get Started
    • What Is ScyllaDB Operator?
    • ScyllaDB Concepts on Kubernetes
  • Install Operator
    • Provision infrastructure
      • Set up a GKE cluster for ScyllaDB
      • Set up an EKS cluster for ScyllaDB
      • Set up an OKE cluster for ScyllaDB
      • Set up an OpenShift cluster for ScyllaDB
    • Install with GitOps
    • Install with Helm
    • Install on OpenShift
  • Deploy ScyllaDB
    • Before you deploy
      • Set up dedicated node pools
      • Configure CPU pinning
      • Configure nodes
      • Configure ScyllaDB Operator
    • Deploy your first cluster
    • Reference deployments
      • Reference deployment: GKE
      • Reference deployment: EKS
      • Reference deployment: OKE
      • Reference deployment: OpenShift
    • Install ScyllaDB Manager
    • Set up networking
      • Configure external access
      • IPv6 networking
        • Getting started with IPv6 networking
        • Configure dual-stack networking
        • Configure IPv6-only networking
        • Migrate clusters to IPv6
        • Troubleshoot IPv6 networking issues
        • IPv6 networking concepts
    • Set up monitoring
      • Set up ScyllaDB Monitoring
      • Set up ScyllaDB Monitoring on OpenShift
      • Expose Grafana
    • Production checklist
  • Connect Your App
    • Connect via CQL
    • Alternator (DynamoDB API)
    • Discovery endpoint
  • Understand
    • Storage
    • Tuning
    • ScyllaDB Manager
    • Networking
    • ScyllaDB Monitoring overview
    • Bootstrap synchronisation
    • Automatic data cleanup
    • Sidecar and pod anatomy
    • Ignition
    • Pod disruption budgets
    • Security
    • StatefulSets and racks
  • Operate
    • Scale, add, remove racks
    • Replace nodes
    • Expand storage volumes
    • Use maintenance mode
    • Back up and restore
    • Restore from backup
    • Perform a rolling restart
    • Migrate a rack to a new node pool
    • Pass additional ScyllaDB arguments
    • Configure precomputed IO properties
  • Upgrade
    • Upgrading ScyllaDB Operator
    • Upgrading ScyllaDB clusters
  • Troubleshoot
    • Investigate pod restarts
    • Change log level on a live cluster
    • Recover from a failed node replace
    • Troubleshoot performance
    • Collect debugging information
      • Collect data with must-gather
      • must-gather contents
      • Query system tables for debugging
    • Collect core dumps
  • Reference
    • API Reference
      • scylla.scylladb.com
        • NodeConfig (scylla.scylladb.com/v1alpha1)
        • RemoteKubernetesCluster (scylla.scylladb.com/v1alpha1)
        • RemoteOwner (scylla.scylladb.com/v1alpha1)
        • ScyllaCluster (scylla.scylladb.com/v1)
        • ScyllaDBCluster (scylla.scylladb.com/v1alpha1)
        • ScyllaDBDatacenterNodesStatusReport (scylla.scylladb.com/v1alpha1)
        • ScyllaDBDatacenter (scylla.scylladb.com/v1alpha1)
        • ScyllaDBManagerClusterRegistration (scylla.scylladb.com/v1alpha1)
        • ScyllaDBManagerTask (scylla.scylladb.com/v1alpha1)
        • ScyllaDBMonitoring (scylla.scylladb.com/v1alpha1)
        • ScyllaOperatorConfig (scylla.scylladb.com/v1alpha1)
    • Feature gates
    • IPv6 configuration reference
    • Releases
    • Known issues
    • Conditions reference
    • nodetool alternatives
  • Contributing to ScyllaDB Operator
Docs Tutorials University Contact Us About Us
© 2026, ScyllaDB. All rights reserved. | Terms of Service | Privacy Policy | ScyllaDB, and ScyllaDB Cloud, are registered trademarks of ScyllaDB, Inc.
Last updated on 22 May 2026.
Powered by Sphinx 9.1.0 & ScyllaDB Theme 1.9.2