You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+53-23Lines changed: 53 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,7 @@
1
1
# telemetry-controller
2
-
// TODO(user): Add simple overview of use/purpose
3
-
2
+
The Telemetry Controller is a multi-tenancy focused solution, that facilitates collection of telemetry data from Kubernetes workloads, without any need for changes to the running software.
4
3
## Description
5
-
// TODO(user): An in-depth paragraph about your project and overview of use
6
-
4
+
Telemetry-controller can be configured using Custom Resources to set up an opinionated Opentelemetry Collector configuration to route log messages based on rules defined as a Tenant -> Subscription relation map.
7
5
## Getting Started
8
6
9
7
### Prerequisites
@@ -13,51 +11,72 @@
13
11
- Access to a Kubernetes v1.11.3+ cluster.
14
12
15
13
### To Deploy on the cluster
16
-
**Build and push your image to the location specified by `IMG`:**
17
14
15
+
**Install cert-manager, and opentelemtry-operator:**
18
16
```sh
19
-
make docker-build docker-push IMG=<some-registry>/telemetry-controller:tag
**Deploy the Manager to the cluster with the image specified by `IMG`:**
33
35
34
36
```sh
35
-
make deploy IMG=<some-registry>/telemetry-controller:tag
37
+
make deploy IMG=telemetry-controller:tag
36
38
```
37
39
38
40
> **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin
39
41
privileges or be logged in as admin.
40
42
41
43
**Create instances of your solution**
42
-
You can apply the samples (examples) from the config/sample:
44
+
You can deploy the example configuration provided as part of the docs. This will deploy a demo pipeline with one tenant, two subscriptions, and an OpenObserve instance.
45
+
Deploying Openobserve is an optional, but recommended step, logs can be forwarded to any OTLP endpoint. Openobserve provides a UI to visualize the ingested logstream.
0 commit comments