-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
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
Remove ComponentUseLocalHostAsDefaultHost() #3306
Comments
yes! |
Is there any way to prevent this feature flag from being added to the produced resources w/o a new release? I'm trying to overcome an issue similar to this one for the helm chart from the install manifests. open-telemetry/opentelemetry-helm-charts#1339 |
@ryanmt we will need to do a new release as that's how the images get published, though i guess you could use the image from main. We haven't released 0.110.0 yet, so i would recommend not misaligning those versions. |
Hi, |
@henrikrexed @frzifus is on it right now and will be done hopefully by EOW this week. |
Related issue Dynatrace/dynatrace-otel-collector#311. The feature flag was fully moved to stable in OTel upstream, waiting for a new upstream release to backport the changes to dynatrace-otel-collector. |
Component(s)
collector
What happened?
Description
The
ComponentUseLocalHostAsDefaultHost()
function should be removed at this point... the operator forces thecomponent.UseLocalHostAsDefaultHost
flag to be added. The problem is that in the OTEL Collector 0.110.0, that flag is no longer settable:Kubernetes Version
1.30.0
Operator version
0.109.0
Collector version
1.111.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: