You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried configured the services for the jaeger collector helm chart deployment - specifically otlp http.
When I was just configuring otlp http, without defining the grpc block too, I run into: Error: UPGRADE FAILED: failed to create resource: Service "jaeger-collector" is invalid: spec.ports[2].name: Required value
Not sure if this is intended, just want to leave the report here.
Steps to reproduce
Deploy helm chart with only otlp http configured for collector
Expected behavior
If intended - would like to only configure the http collector if the grpc is not needed.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
helmchart 0.71.17
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
Kubernetes
Deployment configs
No response
The text was updated successfully, but these errors were encountered:
What happened?
I tried configured the services for the jaeger collector helm chart deployment - specifically otlp http.
When I was just configuring otlp http, without defining the grpc block too, I run into:
Error: UPGRADE FAILED: failed to create resource: Service "jaeger-collector" is invalid: spec.ports[2].name: Required value
Not sure if this is intended, just want to leave the report here.
Steps to reproduce
Deploy helm chart with only otlp http configured for collector
Expected behavior
If intended - would like to only configure the http collector if the grpc is not needed.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
helmchart 0.71.17
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
Kubernetes
Deployment configs
No response
The text was updated successfully, but these errors were encountered: