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
fix: OB-41415 send sidecar metrics to observe directly
Customers have been requesting that we support EKS fargate hosted clusters.
To do this, I add a new fargate mode (off my default) that will install an
otel operator, which will use a sidecar container to query metrics from the
pod it is attached to.
| node.enabled | bool |`true`| Enables the node-logs-metrics agent daemonset for collection of node logs and metrics. The nodes on which metrics and logs are collected can be configured via `affinity` in the `node-logs-metrics` section below. This should be set to false to disable the node-log-metrics daemonset when running in a serverless environment (ex: EKS Fargate). |
558
+
| node.fargateMode | bool |`false`| Enables collection of metrics from EKS Fargate pods. Off by default |
Copy file name to clipboardExpand all lines: charts/agent/values.yaml
+3-31Lines changed: 3 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,8 @@ node:
47
47
# -- Enables the node-logs-metrics agent daemonset for collection of node logs and metrics.
48
48
# The nodes on which metrics and logs are collected can be configured via `affinity` in the `node-logs-metrics` section below.
49
49
# This should be set to false to disable the node-log-metrics daemonset when running in a serverless environment (ex: EKS Fargate).
50
-
enabled: false
50
+
enabled: true
51
+
# -- Enables collection of metrics from EKS Fargate pods. Off by default
51
52
fargateMode: false
52
53
# collects host level metrics from node
53
54
metrics:
@@ -101,7 +102,6 @@ node:
101
102
# this resolves issues similar to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/26481#issuecomment-1720797914 for `no such host` or `connection refused`.
102
103
useNodeIp: false
103
104
forwarder:
104
-
mode: deployment
105
105
enabled: true
106
106
traces:
107
107
enabled: true
@@ -231,10 +231,6 @@ agent:
231
231
# exporters:
232
232
# - otlphttp/extra
233
233
# - otlphttp/observe/forward/trace
234
-
235
-
# -- Additional OTel collector config for fargate-sidecar-metrics custom resource
236
-
fargateSidecarMetrics:
237
-
# Put any OTel config overrides here.
238
234
239
235
# -- Additional OTel collector config for gateway deployment
240
236
gateway:
@@ -957,7 +953,7 @@ monitor:
957
953
forwarder:
958
954
# -- The forwarder is run as a daemonset by default, but can be run as a deployment by setting mode to "deployment". Deployment mode
959
955
# must be used when running in a serverless environment (ex: EKS Fargate) where daemonsets are not supported.
960
-
mode: deployment
956
+
mode: daemonset
961
957
962
958
# -- The `replicaCount` is only used when `mode` is set to "deployment". It is ignored when `mode` is set to "daemonset".
963
959
# In deployment mode, this sets the number of replicas (ie the number of forwarder pods to run).
@@ -1251,27 +1247,3 @@ gateway:
1251
1247
- name: observe-agent-deployment-config
1252
1248
mountPath: /observe-agent-conf
1253
1249
# ----------------------------------------- #
1254
-
image:
1255
-
repository: "otel/opentelemetry-collector-k8s"
1256
-
1257
-
1258
-
fargate-sidecar-injector:
1259
-
1260
-
# -- This is an otel operator that will inject a sidecar container into all pods in the cluster. This is only needed when running
1261
-
# in a serverless environment (ex: EKS Fargate) where daemonsets are not supported.
1262
-
1263
-
replicaCount: 1
1264
-
1265
-
# ----------------------------------------- #
1266
-
# Different for each deployment/daemonset #
1267
-
nameOverride: "fargate-sidecar-injector"
1268
-
# !!! IMPORTANT !!! This needs to have same value as namespaceOverride in cluster above
1269
-
namespaceOverride: "observe"
1270
-
# for now, use defaults for the rest of the values
0 commit comments