it-at-m/helm-charts

[dave] Improve Elasticsearch integration

Open

#106 opened on Mar 21, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Go Template (6 forks)auto 404
davehelp wanted

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

The chart currently deploys the Bitnami Elasticsearch chart as a subchart. However, it isn't automatically integrated into the main application:

  1. The subchart by default disables HTTPS, but DAVe requires HTTPS. Hence we need to set elasticsearch.security.enabled: true and elasticsearch.security.tls.autoGenerated: true
  2. The CA cert fingerprint needs to be manually entered in the backend.extraEnvVars.env["elasticsearch.http-ca-certificate"] value
  3. The password needs to be specified manually in two subcharts (backend.credentials.ELASTICSEARCH_PASSWORD and elasticsearch.security.elasticPassword)
    • This can be mitigated by using #105

I'm still missing a smart way to automate the second point. Maybe a Job that reads the CA cert from the Kubernetes Secret and writes the Fingerprint into a ConfigMap, that can then be read into an environment variable?

Contributor guide

Research direction
Investigate how to automate reading the CA certificate fingerprint from the Kubernetes Secret and writing it into a ConfigMap, then mount it as an environment variable. Look at existing Helm chart patterns for similar automation, such as using init containers or Helm hooks.
Tech stack
kuberneteselasticsearch
Domain
devopsinfrastructurebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesHelm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40