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

Abierto
  • ¿Algo no está bien?
#67 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
helm, java, kubernetes, postgresql, redis
Área
devops, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Java
Estrellas
35
Forks
7
Merge medio
10 h 5 min
PR fusionados (30 d)
179

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devops-thiago/ThrillhouseBot

Todos los issues de devops-thiago/ThrillhouseBot

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.