Allow for Elasticsearch Virtual service to be created

Had a community-contributor request the possibility to create a virtual service via the .values file similar to how a kibana-VS is currently deployed

Example:

apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: elasticsearch
  namespace: logging
spec:
  hosts:
  - "example.com"
  gateways:
  - istio-system/public
  http:
  - route:
    - destination:
        host: logging-ek-es-http.logging.svc.cluster.local
        port:
          number: 9200

added community-contribution elasticsearchKibana teamObservability labels

added kindenhancement label

changed title from Allow for Elasticsearch Virtual service to be created ``` to Allow for Elasticsearch Virtual service to be created

added triage-priority label

added priority6 label

removed triage-priority label

added statusready-to-work label

assigned to @dhilgaertner2

changed iteration to Big Bang Iterations Mar 5, 2024 - Mar 18, 2024

set weight to 3

@jeffv question; this is already possible using the bigbang values. For example; you can add a custom hostname to a virtual service via bb-values->elasticsearchKibana->values->istio->kibana->hosts. Would we like to expose this in the bigbang chart or would additional documentation on how to configure the above be sufficient?

Also; perhaps this is about creating a completely separate virtual service. I just want to make sure before I begin.

@jeffv nvm I think i figured out what we need here.

added statusdoing label and removed statusready-to-work label

mentioned in merge request !202 (merged)

added statusreview label and removed statusdoing label

mentioned in merge request big-bang/bigbang!3973 (merged)

removed iteration Big Bang Iterations Mar 5, 2024 - Mar 18, 2024

changed iteration to Big Bang Iterations Mar 19, 2024 - Apr 1, 2024

removed weight of 3

set weight to 4

changed weight to 6 from 4

Seems like this requires some work in terms of the built in ElasticSearch security settings which are enabled by default. ElasticSearch seems to want HTTPS termination at its level and not istio. I believe this might need an xpack carve out; but not entirely sure how to do so without inadvertently causing a security issue. Looking into this.

added statusdoing label and removed statusreview label

changed weight to 8 from 6

Finally done

removed statusdoing label

added statusreview label

removed iteration Big Bang Iterations Mar 19, 2024 - Apr 1, 2024

changed iteration to Big Bang Iterations Apr 2, 2024 - Apr 15, 2024

closed with merge request big-bang/bigbang!3973 (merged)

mentioned in commit big-bang/bigbang@611675cd