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
We are using tempo-operatorv0.9.0 and having issues with the new feature added to define affinity and tolerations.
We can add them to the CR instance, but the operator does not respect the values when creating the statefulset instance.
Output from the applied CR instance named cluster:
$ k get tempomonolithics.tempo.grafana.com cluster -o yaml | yq '.spec.affinity'nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: node-role.kubernetes.io/observabilityoperator: Exists$ k get tempomonolithics.tempo.grafana.com cluster -o yaml | yq '.spec.tolerations'
- effect: NoSchedulekey: dedicatedoperator: Equalvalue: observability
$ k exec -it tempo-cluster-0 -- ./tempo --version
tempo, version 2.3.1 (branch: HEAD, revision: 9398fd620)
build user:
build date:
go version: go1.21.3
platform: linux/amd64
tags: unknown
$ k get pod tempo-cluster-0 -o yaml | yq '.spec.containers[].image'
docker.io/grafana/tempo:2.3.1
$ k get pod tempo-operator-controller-5f545dd674-gfqm5 -o yaml | yq '.spec.containers[].image'
ghcr.io/grafana/tempo-operator/tempo-operator:v0.9.0
gcr.io/kubebuilder/kube-rbac-proxy:v0.13.0
We are using tempo-operator
v0.9.0
and having issues with the new feature added to defineaffinity
andtolerations
.We can add them to the CR instance, but the operator does not respect the values when creating the statefulset instance.
Output from the applied CR instance named
cluster
:And the statefulset created from the operator:
And just for confirmation, CRD property parsing:
The text was updated successfully, but these errors were encountered: