Validate, publish and promote nextcloud-whiteboard chart / chart (push) Successful in 37s
30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
# Nextcloud Whiteboard
|
|
|
|
This repository maintains a portable Helm chart for the Nextcloud Whiteboard integration.
|
|
It is used with the upstream Nextcloud Helm release. The application image is
|
|
`ghcr.io/nextcloud-releases/whiteboard:v2.0.0`; the chart selects that tested tag through
|
|
`Chart.yaml.appVersion`, while GitOps selects only the chart version.
|
|
|
|
The chart requires a Secret containing the same JWT key configured in Nextcloud.
|
|
|
|
```sh
|
|
helm repo add brunner.ninja https://brunner.ninja/charts
|
|
helm repo update brunner.ninja
|
|
VALUES_FILE=values.yaml ./install.sh
|
|
```
|
|
|
|
The chart and its templates own the Kubernetes workload contract; set hostnames,
|
|
Ingress annotations, resources, and Secret names through values. The live
|
|
[homelab configuration](https://code.brunner.ninja/feedc0de/homelab-gitops/src/branch/main/apps/nextcloud)
|
|
is an example, not a portable default. Run `bash chart/test.sh` before
|
|
publishing.
|
|
|
|
The Git tag follows the actual upstream release `v2.0.0`. Its first chart
|
|
package is `2.0.0`; later chart-only commits append the commit count
|
|
and Git hash. CI publishes the package to the indexed
|
|
`https://brunner.ninja/charts` repository and promotes only this chart's
|
|
Argo CD targetRevision.
|
|
|
|
The homelab deployment was adopted in place, retaining the live resource
|
|
identities; later chart-only changes are published and promoted by CI.
|