-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
None
-
1
-
False
-
None
-
False
-
-
-
Tracing Sprint # 246
Versions of components:
tempo-operator.v0.5.0
Description of the problem:
The queryFrontend component in TempoStack is not scaling when we increase the replica count for the component.
Steps to reproduce the issue:
*Create a TempoStack with queryFrontend replicas set to 2 or more replicas.
apiVersion: tempo.grafana.com/v1alpha1
kind: TempoStack
metadata:
name: tempostack
namespace: tracing-system
spec:
limits:
global:
ingestion: {}
query:
maxSearchDuration: 0s
managementState: Managed
observability:
metrics: {}
tracing:
jaeger_agent_endpoint: 127.0.0.1:6831
replicationFactor: 1
resources:
total:
limits:
cpu: "2"
memory: 4Gi
requests:
cpu: "1"
memory: 1Gi
retention:
global:
traces: 48h0m0s
search:
defaultResultLimit: 20
maxDuration: 0s
serviceAccount: tempo-tempostack
storage:
secret:
name: minio-secret
type: s3
tls: {}
storageSize: 20Gi
template:
compactor: {}
distributor:
replicas: 1
gateway:
component: {}
enabled: false
ingress:
route: {}
ingester:
replicas: 1
querier:
replicas: 1
queryFrontend:
component:
replicas: 2
jaegerQuery:
enabled: true
ingress:
route: {}
monitorTab:
enabled: false
prometheusEndpoint: ""
*Create the TempoStack and check the component replica count is 1 and its not scaled.
$ oc describe deployment tempo-tempostack-query-frontend | grep Replicas: Replicas: 1 desired | 1 updated | 1 total | 1 available | 0 unavailable
- links to
-
RHSA-2023:125604
Red Hat OpenShift distributed tracing 3.1.0 operator/operand containers
