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: logs/README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,8 @@ You can install the `Logs` package in your cluster by installing it with [Helm](
51
51
52
52
**Step 2:**
53
53
54
-
The package will deploy the OpenTelemetry Operator which works as a manager for the collectors and auto-instrumentation of the workload. By default, the package will include a configuration for collecting metrics and logs. The log-collector is currently processing data from the [preconfigured receivers](#Overview):
54
+
You can choose if you want to deploy the OpenTelemetry Operator including the collectors or set `opentelemetry-operator.enabled` to `false` in case you already have an existing Operator deployed in your cluster. The OpenTelemetry Operator works as a manager for the collectors and auto-instrumentation of the workload.
55
+
By default, the package will include a configuration for collecting metrics and logs. The log-collector is currently processing data from the [preconfigured receivers](#Overview):
55
56
- Files via the Filelog Receiver
56
57
- Kubernetes Events from the Kubernetes API server
57
58
- Journald events from systemd journal
@@ -80,7 +81,11 @@ The **Logs** Plugin comes with a [Failover Connector](https://github.com/open-te
80
81
| Key | Type | Default | Description |
81
82
|-----|------|---------|-------------|
82
83
| commonLabels | object |`{}`| common labels to apply to all resources. |
84
+
| customCRDs.enabled | bool |`true`| The required CRDs used by this dependency are version-controlled in this repository under ./charts/crds. |
83
85
| openTelemetry.cluster | string |`nil`| Cluster label for Logging |
| openTelemetry.collectorImage.tag | string |`"2016982"`| Image tag for OpenTelemetry Collector |
84
89
| openTelemetry.customLabels | object |`{}`| custom Labels applied to servicemonitor, secrets and collectors |
85
90
| openTelemetry.logsCollector.cephConfig | object |`{"enabled":false}`| Activates the configuration for Ceph logs (requires logsCollector to be enabled). |
86
91
| openTelemetry.logsCollector.enabled | bool |`true`| Activates the standard configuration for Logs. |
@@ -107,10 +112,9 @@ The **Logs** Plugin comes with a [Failover Connector](https://github.com/open-te
107
112
| opentelemetry-operator.admissionWebhooks.autoGenerateCert.recreate | bool |`false`| Activate to recreate the cert after a defined period (certPeriodDays default is 365). |
108
113
| opentelemetry-operator.admissionWebhooks.certManager | object |`{"enabled":false}`| Activate to use the CertManager for generating self-signed certificates. |
109
114
| opentelemetry-operator.admissionWebhooks.failurePolicy | string |`"Ignore"`| Defines if the admission webhooks should `Ignore` errors or `Fail` on errors when communicating with the API server. |
110
-
| opentelemetry-operator.crds.create | bool |`false`| The required CRDs used by this dependency are version-controlled in this repository under ./crds. If you want to use the upstream CRDs, set this variable to `true``. |
115
+
| opentelemetry-operator.crds.create | bool |`false`| If you want to use the upstream CRDs, set this variable to `true``. |
116
+
| opentelemetry-operator.enabled | bool |`true`| Set to true to enable the installation of the OpenTelemetry Operator. |
111
117
| opentelemetry-operator.kubeRBACProxy | object |`{"enabled":false}`| the kubeRBACProxy can be enabled to allow the operator perform RBAC authorization against the Kubernetes API. |
112
-
| opentelemetry-operator.manager.collectorImage.repository | string |`"ghcr.io/cloudoperators/opentelemetry-collector-contrib"`| overrides the default image repository for the OpenTelemetry Collector image. |
113
-
| opentelemetry-operator.manager.collectorImage.tag | string |`"2016982"`| overrides the default image tag for the OpenTelemetry Collector image. |
114
118
| opentelemetry-operator.manager.image.repository | string |`"ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"`| overrides the default image repository for the OpenTelemetry Operator image. |
115
119
| opentelemetry-operator.manager.image.tag | string |`"v0.131.0"`| overrides the default tag repository for the OpenTelemetry Operator image. |
Copy file name to clipboardExpand all lines: logs/README.md.gotmpl
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,8 @@ You can install the `Logs` package in your cluster by installing it with [Helm](
51
51
52
52
**Step 2:**
53
53
54
-
The package will deploy the OpenTelemetry Operator which works as a manager for the collectors and auto-instrumentation of the workload. By default, the package will include a configuration for collecting metrics and logs. The log-collector is currently processing data from the [preconfigured receivers](#Overview):
54
+
You can choose if you want to deploy the OpenTelemetry Operator including the collectors or set `opentelemetry-operator.enabled` to `false` in case you already have an existing Operator deployed in your cluster. The OpenTelemetry Operator works as a manager for the collectors and auto-instrumentation of the workload.
55
+
By default, the package will include a configuration for collecting metrics and logs. The log-collector is currently processing data from the [preconfigured receivers](#Overview):
55
56
- Files via the Filelog Receiver
56
57
- Kubernetes Events from the Kubernetes API server
0 commit comments