Issue
When using Elasticsearch for the storage of Jaeger in OSSM, the node selector settings are not reflected in Elasticsearch deployments.
$ oc edit smcp/basic -n istio-system
runtime:
components:
tracing.jaeger.elasticsearch:
nodeSelector:
node-role.kubernetes.io/infra: ''
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/infra
value: reserved
- effect: NoExecute
key: node-role.kubernetes.io/infra
value: reserved
And deleting the corresponding Elasticsearch deployment does not trigger automatic recreation by Elasticsearch Operator.
$ oc delete deploy -n istio-system elasticsearch-cdm-istiosystemjaeger-1
deployment.apps "elasticsearch-cdm-istiosystemjaeger-1" deleted
$ oc get deploy -n istio-system -l cluster-name=elasticsearch
NAME READY UP-TO-DATE AVAILABLE AGE
elasticsearch-cdm-istiosystemjaeger-2 1/1 1 0 2m4s
elasticsearch-cdm-istiosystemjaeger-3 1/1 1 0 102s
New to Red Hat?
Learn more about Red Hat subscriptions
Using a Red Hat product through a public cloud?
How to access this content
Here are the common uses of Markdown.
Code blocks ~~~
Code surrounded in tildes is easier to read
Links/URLs [Red Hat Customer Portal](https://access.redhat.com)
Learn more
Close
Are you sure you want to request a translation?
We appreciate your interest in having Red Hat content localized to your language. Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated.
Close