replicatedhq / replicatedhq/platform-examples

feat(gitea): add development-values.yaml for headless installation support

Open
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
9
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Summary

The gitea application is missing a development-values.yaml file (a ConfigValues kind) that would enable headless installations and CI/CD automation via kubectl kots install --config-values.

Context

The storagebox application in this monorepo establishes a "four-way contract" pattern between:

  1. development-values.yaml - ConfigValues for headless installations
  2. kots/kots-config.yaml - Admin Console configuration UI
  3. kots/<app>-chart.yaml - HelmChart CR with KOTS template functions
  4. charts/<app>/values.yaml - Base Helm chart values

The gitea application currently has items 2-4 but is missing item 1. This was identified during the Bitnami-to-CNPG/Valkey migration (replacing Bitnami PostgreSQL and Redis with CloudNativePG and Valkey).

Proposed File

Create applications/gitea/development-values.yaml:

apiVersion: kots.io/v1beta1
kind: ConfigValues
metadata:
  name: gitea-config-values
spec:
  values:
    internal_postgres_enabled:
      default: "1"
      value: "1"
    postgres_db:
      default: "gitea"
      value: "gitea"
    postgres_user:
      default: "gitea"
      value: "gitea"
    postgres_password:
      default: "gitea"
      value: "gitea"
    postgres_host:
      default: "gitea-postgres-rw:5432"
      value: "gitea-postgres-rw:5432"
    internal_valkey_enabled:
      default: "1"
      value: "1"
    valkey_password:
      default: "changeme"
      value: "changeme"

Benefits

  • Enables headless installation for CI/CD pipelines
  • Maintains consistency with the storagebox four-way contract pattern
  • Documents expected default values in a machine-readable format

Contributor guide

Open the contributing guide

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.

Research direction

Create applications/gitea/development-values.yaml as a ConfigValues resource. Compare the storagebox development-values.yaml pattern with applications/gitea/kots/kots-config.yaml, applications/gitea/kots/-chart.yaml, and charts/gitea/values.yaml, then verify the listed PostgreSQL and Valkey values support the documented kubectl kots install --config-values workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
ci-cd, devops
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.