We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elastic's k8s OTel Operator docs show the steps to install and upgrade, e.g.: https://github.com/elastic/opentelemetry/tree/main/docs/kubernetes/operator#operator-installation
This includes using (at the time of writing): https://raw.githubusercontent.com/elastic/opentelemetry/refs/heads/8.16/resources/kubernetes/operator/helm/values.yaml
That values.yaml file includes a hardcoded version of the EDOT Node.js docker image to use, currently:
nodejs: image: docker.elastic.co/observability/elastic-otel-node:0.4.1
That value should get updated after a new release. Let's document that process (and perhaps automate it).
The text was updated successfully, but these errors were encountered:
Note: This doc also includes those versions, which should probably be updated: https://github.com/elastic/opentelemetry/blob/main/docs/kubernetes/operator/instrumenting-applications.md#auto-instrumentation-basics
Sorry, something went wrong.
No branches or pull requests
Elastic's k8s OTel Operator docs show the steps to install and upgrade, e.g.: https://github.com/elastic/opentelemetry/tree/main/docs/kubernetes/operator#operator-installation
This includes using (at the time of writing):
https://raw.githubusercontent.com/elastic/opentelemetry/refs/heads/8.16/resources/kubernetes/operator/helm/values.yaml
That values.yaml file includes a hardcoded version of the EDOT Node.js docker image to use, currently:
That value should get updated after a new release. Let's document that process (and perhaps automate it).
The text was updated successfully, but these errors were encountered: