opentelemetry-helm-charts
opentelemetry-helm-charts copied to clipboard
OpenTelemetry Helm Charts
Error: failed to start container "opentelemetry-collector": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/otelcol-contrib": stat /otelcol-contrib: no such file or directory: unknown
in _pod.tpl ```yaml livenessProbe: httpGet: path: / port: 13133 readinessProbe: httpGet: path: / port: 13133 ``` But port 13133 is not exposed
Hi everyone! I opened a PR for add custom rollout update in daemonset (agentCollector) In some cases could be necessary change default values in rollout update. For example. If I...
Hello, I understand that you wanted to provide a "base configuration" (`config`) and an overridable one (`standaloneCollector.configOverride` or `agentCollector.configOverride`) and it's very useful. But there is a problem because setting...
The Operator chart deployment template should support the priorityClassName attribute. This is required in cases where pods are restarted including the operator, the operator should start first before other pods...
Catching issues like the one fixed in this PR makes sense. Probably we can have a matrix of popular helm versions in the [lint-test job](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/.github/workflows/lint-test.yaml). __Originally posted by @dmitryax in...
## How it behaves Processor is not defined. ## How it should behave Processor should be defined. ## Reproduction ### Configuration ```yaml config: receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 processors:...
Need a way to load the api-key into the config. Dont want to stick an api-key into the config section of the values file.
Hey guys, I'm implementing opentelemetry and every time I access this repo a new version exists (at least a bug fix version). It is really difficult to know what is...
I am currently testing the prometheus receiver. The chart creates a service account with no specific permission, therefore I faced the classical `Failed to watch *v1.Service` Which is the recommended...