Splunk POD release notes
For information on the Splunk POD version 2.0 release, see
Supported Splunk Enterprise versions
Splunk POD 2.0 supports Splunk Enterprise versions 10.4.2 and 10.2.7. For details on Splunk POD versioning syntax, see Splunk POD versioning.
What's new in 2.0
Feature enhancements for Splunk POD version 2.0
Splunk POD version 2.0, released on August 31, 2026, includes the following enhancements:
| New Feature | Description |
|---|---|
| Migration to Ceph storage | Splunk POD now uses Rook-Ceph (Ceph) for block and S3-compliant object storage. Ceph offers a more resilient distributed architecture that gives Splunk components more flexibility to relocate, and improves both scalability and recovery from node failures. For more information, see Splunk POD architecture. |
| Simplified POD hardware | Splunk POD hardware requirements are simplified and less costly with the migration to Ceph. NVMe-based deployments require fewer servers and drives, and Splunk POD also adds a new lower-priced HDD option. See Node hardware requirements. |
| External S3 provider support | Splunk POD now supports configuring an external, customer-managed S3-compatible storage provider for object storage, as an alternative to the internal Ceph object store. See Configure external S3 providers. |
| Monitoring enhancements | Splunk POD now provides expanded Perses dashboards with additional Prometheus metrics and alerts for monitoring cluster and storage health. See Monitor Splunk POD. |
| FIPS compliance | Splunk POD now supports FIPS 140-3 compatibility mode. Federal Information Processing Standards (FIPS) 140-3 defines U.S. government requirements for cryptographic functions, such as encryption and key management. For more information, see FIPS compliance. |
Known issues
| Date filed | Issue number | Description |
|---|---|---|
| 2026-01-15 | EIST-574 |
Missing CoreDNS deployment, leading to CoreDNS pods missing. This issue can appear during initial cluster deployment but does not appear during deployment on an existing cluster. Symptoms include no CoreDNS Kubernetes pods present and Splunk pods not ready. Workaround: Retry |
| 2026-08-2024 | EIST-989 | Running -destroy is slow and can take excess of 20 minutes.
This issue does not block |