[Openshift 4.6] [Jaeger] [Elasticsearch] Clarification on Jaeger external elasticsearch connection

[sreenichelikam]

Which section(s) is the issue in?

Observed the option in documentation to configure the external elasticsearch url (using server-urls) while provisioning the Jeager CR. Below are the links and section names for reference. https://docs.openshift.com/container-platform/4.6/jaeger/jaeger_install/rhbjaeger-deploying.html#jaeger-config-storage_jaeger-deploying Section/table : Elasticsearch configuration parameters Section : Storage example with volume mounts

But also observed statement in known issues, saying "Only self-provisioned Elasticsearch instances are supported. External Elasticsearch instances are not supported in this release." Below is the link https://docs.openshift.com/container-platform/4.6/jaeger/rhbjaeger-release-notes.html#jaeger-rn-known-issues_jaeger-release-notes

What needs fixing?

is Jaeger support external elasticsearch connection in Openshift 4.6 version?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/27031#issuecomment-826179708): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.