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
alternateConfig
The text was updated successfully, but these errors were encountered:
Happy to help with this issue. It will be using openTelemetry operator installed by helm, right?
Sorry, something went wrong.
I don't think so, the upstream and the Elastics fork uses the open-telemetry/opentelemetry-demo Helm Chart, which uses the open-telemetry/opentelemetry-collector Chart to deploy the collector. The last, does not use the operator but raw daemonset and/or deployments.
No branches or pull requests
Local
K8s
alternateConfig
section within the Helm values file so user can easily locate/modify them.The text was updated successfully, but these errors were encountered: