Splunk Dev

How to ingest data from specific namespace in OpenShift using Splunk Connect for Kubernetes?

Amusthofa
Explorer

Hi, folks.

We were trying to ingest data from Openshift using Splunk Connect for Kubernetes. So far we have succeeded in ingesting from the whole infrastructure. So we are wondering if we can limit from which specific namespaces we are going to ingest data from.

As far as I understood from this link (https://github.com/splunk/splunk-connect-for-kubernetes#managing-sck-log-ingestion-by-using-annotati...), it tells us how to route data per namespaces to specific indexes but still collecting from all namespaces.

Our goal is currently to collect only from certain namespaces, e.g. just from 2 namespaces instead of all of them.  Is it possible to do with the add-on? Did I miss some detailed explanations?

Please advise.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...