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
Deploy a ThanosRuler resource named foo in namespace default with 1 replica.
Resolve the thanos-ruler-foo-0.thanos-operated.default.cluster.local` name inside the Thanos ruler container.
The name can't be resolved.
Did you expect to see something different?
The name should be resolved to the IP of the pod.
How to reproduce it (as minimally and precisely as possible):
See above.
Environment
Prometheus Operator version: main
Kubernetes version information: N/A
Kubernetes cluster kind: N/A
Manifests: N/A
Prometheus Operator Logs: N/A
Anything else we need to know?:
The operator doesn't set the .spec.serviceName to thanos-operator in the statefulset.
Though the Kubernetes documentation states that service name is mandatory, an empty value is valid (see kubernetes/kubernetes#69608) hence we didn't catch it before. In practice, it only causes an issue if you want to resolve the IP address of an individual pod but to configure a Thanos query, you would use the DNSSRV records of the service which return the expected result.
The text was updated successfully, but these errors were encountered:
What happened?
foo
in namespacedefault
with 1 replica.the
thanos-ruler-foo-0.thanos-operated.default.cluster.local` name inside the Thanos ruler container.The name can't be resolved.
Did you expect to see something different?
The name should be resolved to the IP of the pod.
How to reproduce it (as minimally and precisely as possible):
See above.
Environment
Prometheus Operator version: main
Kubernetes version information: N/A
Kubernetes cluster kind: N/A
Manifests: N/A
Prometheus Operator Logs: N/A
Anything else we need to know?:
The operator doesn't set the
.spec.serviceName
tothanos-operator
in the statefulset.Though the Kubernetes documentation states that service name is mandatory, an empty value is valid (see kubernetes/kubernetes#69608) hence we didn't catch it before. In practice, it only causes an issue if you want to resolve the IP address of an individual pod but to configure a Thanos query, you would use the DNSSRV records of the service which return the expected result.
The text was updated successfully, but these errors were encountered: