CodeScoring.Save Installation Options

CodeScoring.Save supports two installation options: a SQLite-based option in k3s and a PostgreSQL-based option in Kubernetes. Both options are installed through the save Helm chart, but they target different infrastructure and operation scenarios.

The Helm repository address and Docker Registry with CodeScoring.Save images are provided by the vendor. Installation examples use the placeholders <HELM_REPOSITORY_URL> and <REGISTRY_HOST>.

Available Options

OptionWhen to use
Hosted installationTesting, demonstrations, small teams, and quick start without separate PostgreSQL and S3 infrastructure
PostgreSQL installationProduction use, scaling, and operation with external or built-in PostgreSQL and S3-compatible storage

Before choosing an option, check installation requirements and prepare a shared values.yaml file. The main parameters are set in these sections:

  • image
  • envs
  • configMaps
  • deploymentsGeneral
  • postgres
  • minio

The image section defines the shared registry, tag, and pull secret for backend, frontend, and auth images. Service environment variables are defined in envs.

To pass values from envs to Pods, enable the envs ConfigMap and attach it to deployments through deploymentsGeneral.envConfigmaps.

Was this page helpful?