ElasticHQ/elasticsearch-HQ

Using Elasticsearch-HQ on Kubernetes with Ingress rules

Open

#473 建立於 2019年5月20日

在 GitHub 查看
 (1 留言) (1 反應) (0 負責人)JavaScript (4,921 star) (532 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.