Stefan-Sanger
e19cc05403
- chart: add secretEnv (existingSecret + keys) rendered as secretKeyRef in both containers; add resourcesProsody/resourcesSidecar defaults with dedicated requests and limits via a containerResources helper - argo: move prosodyDBpass/fcmApiKey/fileShareSecret/avatarUploadPass out of env into secretEnv referencing a prosody-secrets Secret; set dedicated resource requests+limits per container - argo: add prosody-secrets.example.yaml ArgoCD Application (with a warning to use Sealed Secrets / External Secrets / SOPS instead of plaintext) - chart fixes: bump stale appVersion 0.11.6 -> 13.0.6; fix malformed service block in values.yaml Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
24 lines
1.1 KiB
YAML
24 lines
1.1 KiB
YAML
apiVersion: v2
|
|
name: prosody
|
|
description: A Helm chart for Kubernetes
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
|
version: 0.1.0
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application. Versions are not expected to
|
|
# follow Semantic Versioning. They should reflect the version the application is using.
|
|
appVersion: 13.0.6
|