All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 before July 1, 2023 in order to continue to receive full product support from Splunk.
Port configuration requirements
The Splunk Data Stream Processor uses the following ports.
These ports are used for cluster operation and should be open between cluster nodes.
|53||TCP and UDP||Internal cluster DNS|
|2379, 2380||HTTPS||Etcd server communications|
|6443||HTTPS||Kubernetes API Server|
|7498, 9091, 9099||TCP||Calico agents|
|9100||HTTPS||Prometheus Metrics exporter|
|10248 - 10250, 10256, 10257, 10259||HTTPS||Kubernetes components|
Starting in DSP 1.4.0, all external HTTP-based traffic goes to the standard port 443. The following are ports used by end users outside of the cluster. Not all cluster nodes need to be exposed, but the node externally accessible needs to have the following ports open.
|443||Standard port for all HTTP-based traffic.|
|9997||Optional. Standard port used by the Splunk Forwarder service to send data from a Splunk forwarder to a data pipeline.|
Hardware and Software Requirements
Network Encryption Policy
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2, 1.4.3