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.

Sign up for GitHub

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

Jump to bottom

[tempo] bug: Service name is different from the Service name specified in StatefulSets #3042

Open

tozastation opened this issue Mar 26, 2024 · 1 comment

tozastation commented Mar 26, 2024 •

edited

Problem Detail:

StatefulSets resource defines serviceName as ${SERVICE_NAME}-headless
However service name is defined in ${SERVICE_NAME}.
So, name resolution with FQDN in Headless Service is not possible.

Resolution:

Assign a headless suffix to the Service resource name
or
Remove Headless prefix from Service Name in StatefulSet

Reference:

StatefulSet (spec.serviceName)
- https://github.com/grafana/helm-charts/blob/main/charts/tempo/templates/statefulset.yaml#L20
Service (metadata.name)
- https://github.com/grafana/helm-charts/blob/main/charts/tempo/templates/service.yaml#L4

tozastation mentioned this issue

[tempo] bugfix: Service name is different from the Service name specified in … #3043

Open

dastrobu commented Apr 22, 2024

I think there might be more to this:

https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/:

StatefulSets currently require a Headless Service to be responsible for the network identity of the Pods. You are responsible for creating this Service.

The helm chart is currently not defining a headless service.

dastrobu mentioned this issue

[tempo] helm chart is not ready for monolithic scaling #3096

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment