ElasticHQ/elasticsearch-HQ

Using Elasticsearch-HQ on Kubernetes with Ingress rules

Open

#473 opened on 2019年5月20日

GitHub で見る
 (1 comment) (1 reaction) (0 assignees)JavaScript (4,921 stars) (532 forks)batch import
help wanted

説明

General information

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Kubernetes on RedHat Enterprise
  • ElasticHQ Version: release-v3.5.0
  • Browser Vendor and Version (if applicable): Chrome latest

Issue Description

We are running Elastic cluster and Elasticsearch-HQ also single Kubernetes cluster. We ´would like to access the HQ UI thru https:///hq

We would like to configure Kubernetes Ingress to point hq to Elastic-HQ service (service is here Kubernetes service).

Here sample ingress.yml

apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: kibana-http-ingress annotations: namespace: common kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - host: vlcrmed001.at.inside http: paths: - path: /app/kibana backend: serviceName: kibana servicePort: 30601 - path: /auth backend: serviceName: keycloak servicePort: 30085 - path: /hq backend: serviceName: elasticsearch-hq servicePort: 30201

コントリビューターガイド

技術スタック
javascriptkubernetes
領域
devopsinfrastructurecloud
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
basic understanding of Kubernetes Ingressfamiliarity with ElasticHQ deployment
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
The issue requests support for running ElasticHQ behind a Kubernetes Ingress with a subpath (/hq). Currently, ElasticHQ likely serves on root path, so URL rewriting may break asset links. To resolve, investigate if ElasticHQ supports a base URL configuration or if a reverse proxy with path rewriting (e.g., nginx ingress with rewrite target) can be used. The repository is in JavaScript (likely a frontend SPA), so embedding the subpath at build time may be necessary. Check existing documentation or issues for similar configurations. A potential fix could involve adding an environment variable for the base path or updating the frontend routing.