Skip to content

Commit 5ee7d57

Browse files
author
p-hagen-sfx
committed
Extended namespaces txt
1 parent e9aec35 commit 5ee7d57

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/en/tko/session-5/docs/deploy-otel.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ weight: 1
66

77
## 1. Namespaces in Kubernetes
88

9-
Namespaces are a way to organize kubernetes clusters into virtual sub-clusters. They can be helpful when different teams or projects share a Kubernetes cluster.
9+
Namespaces are a way to organize kubernetes clusters into virtual sub-clusters. They can be helpful when different teams or projects share a Kubernetes cluster which usually is the case with larger customers/prospects.
1010

11-
Any number of namespaces are supported within a cluster, each logically separated from others but with the ability to communicate with each other.
11+
Any number of namespaces are supported within a cluster, each logically separated from others but with the ability to communicate with each other. Components are only "visible" when selecting a NameSpace or when adding the --all-namespaces flag instead allowing you to view just the components relevant to your project by selecting your NameSpace.
1212

13-
Most customers will want to install the Splunk OpenTelemetry Collector in a NameSpace. This workshop will follow that practice.
13+
Most customers will want to install the Splunk OpenTelemetry Collector in a separate NameSpace. This workshop will follow that practice.
1414

1515
## 2. Obtain Access Token
1616

0 commit comments

Comments
 (0)