Closed arunkumar-muthusamy-personal closed 1 year ago
Any update on this issue? I am facing same issue when deploying anything past app version 4.5.0. Deployment is setting isolateComponents=false in my case while deploying to EKS.
Any help regarding this would be greatly appreciated.
@jaspreetssethi we have not had time to triage this. What happens if you make changes to the chart locally? Does it work?
@diemol Changing the cart seems to have no effect... tried adding annotation "dynatrace.com/inject: false" and also environment variable of OTEL_SDK_DISABLED="true".
The only thing that worked was to disable Dynatrace deep monitoring on the selenium-* pods entirely. But that is not a good solution IMO.
The only thing that worked was to disable Dynatrace deep monitoring on the selenium-* pods entirely.
Is that something you added to the pods? I am not aware we offer Dynatrace monitoring out of the box.
You provide OpenTelemetry Instrumentation and Dynatrace is one such agent that is configured on our cluster.
How are you enabling the instrumentation? We provide now this docker compose as an example https://github.com/SeleniumHQ/docker-selenium/blob/trunk/docker-compose-v3-tracing.yml
Closing as we did not get an answer.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
Deployed the helm chart as is
helm install selenium-grid docker-selenium/selenium-grid --set isolateComponents=true
on OpenShift v4.9 (Kubernetes version # v1.22.8), router and browser node deployments are failing. Other components are running healthy.Command used to start Selenium Grid with Docker
Relevant log output
browser nodes (example node-chome) failed with following errors: