DoD-Platform-One / elasticsearch-kibana

Deployment of Elasticsearch and Kibana.
https://repo1.dso.mil/big-bang/product/packages/elasticsearch-kibana
Apache License 2.0
1 stars 0 forks source link

Allow for Elasticsearch Virtual service to be created #4

Closed p1-repo-sync-bot[bot] closed 6 months ago

p1-repo-sync-bot[bot] commented 7 months ago

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
p1-repo-sync-bot[bot] commented 7 months ago

dhilgaertner2 commented:

@jeffv question; this is already possible using the bigbang values. For example; you can add a custom hostname to 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?

p1-repo-sync-bot[bot] commented 7 months ago

dhilgaertner2 commented:

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

p1-repo-sync-bot[bot] commented 6 months ago

dhilgaertner2 commented:

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.

p1-repo-sync-bot[bot] commented 6 months ago

dhilgaertner2 commented:

Finally done

p1-repo-sync-bot[bot] commented 6 months ago

Issue 'Allow for Elasticsearch Virtual service to be created' closed from GitLab side