Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(deploy): official Helm chart for Kubernetes (ingress, secrets, bundled/external Redis & Postgres)

Open
  • Is something wrong?
#67 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
helm, java, kubernetes, postgresql, redis
Domain
devops, infrastructure

Research direction

Start by reviewing the existing Docker Compose deployment and the multi-replica work tracked in #23 and #24; the payload does not name repository files or tests. Define and package a Helm chart with configurable app, ingress, secrets, Redis and PostgreSQL settings, health probes, and documented values; done means a repeatable install supports bundled or external data services and defaults to one replica.

Written by the indexing model from the issue text.

Description

enhancement help wanted
Problem Statement

The only documented deployment is Docker Compose (single host). Running on Kubernetes today means hand-writing Deployment/Service/Ingress/Secret manifests and standing up Redis and PostgreSQL separately — there is no supported, repeatable install. This pairs with the 1.0 multi-replica work (#23, #24).

Proposed Solution

Ship an official Helm chart that:

  • Deploys the app (Deployment + Service) with a configurable Ingress (host, TLS, annotations).
  • Sources configuration and secrets from a Kubernetes Secret, with support for an external secret store (e.g. External Secrets Operator or a Secrets Store CSI driver) instead of inlining sensitive values.
  • Bundles optional Redis and PostgreSQL dependencies as subcharts for a one-command install, each disableable so operators can point at external/managed Redis and Postgres via connection config.
  • Wires liveness/readiness probes to the SmallRye health endpoints (/q/health/live, /q/health/ready).
  • Defaults to a single replica until the multi-replica work (#23/#24) lands, then supports replicas: N.
  • Provides a documented values.yaml with sane defaults.
Alternatives Considered
  • Raw manifests / Kustomize — lower abstraction, less reusable than a chart.
  • Docker Compose only (current) — fine for a single host, not for Kubernetes operators.
Priority

Important

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Dominant language
Java
Stars
35
Forks
7
Avg merge
9h 37m
Merged PRs (30d)
148

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devops-thiago/ThrillhouseBot

All issues in devops-thiago/ThrillhouseBot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.