chart: make the default deployment ready to install
Use the CI-published :latest tag with pullPolicy Always, since the chart previously defaulted to appVersion 0.1.0, which is not published as an image. Add ingress annotations with a cert-manager ClusterIssuer so the TLS secret is issued instead of having to exist beforehand. Extend release.sh --deploy to create the registry image pull secret from the local Docker config and pass it to the release, and document both the scripted and manual deployment paths.
This commit is contained in:
1 parent
96d704f192
commit
441fa056ba
5 files changed
+58
-12
No files matched your search
@@ -653,31 +653,53 @@ scripts/release.sh --deploy # also apply the users secret and helm upgrad
|
||||
|
||||
`charts/musicmanager` renders:
|
||||
|
||||
- image repository/tag and `imagePullSecrets`
|
||||
- image repository/tag (defaults to `:latest` with `pullPolicy: Always`) and `imagePullSecrets`
|
||||
- `library.folders` into a ConfigMap (`/etc/musicmanager/library.yaml`)
|
||||
- `users.existingSecret` + key (Vault-managed; never put passwords in values)
|
||||
- ingress host `subsonic.tap-tap.win`, ingress class and TLS secret
|
||||
- ingress host `subsonic.tap-tap.win`, ingress class, annotations and TLS secret;
|
||||
cert-manager issues the certificate with the `letsencrypt-issuer` ClusterIssuer
|
||||
by default
|
||||
- `/data` PVC (size, storage class)
|
||||
- `hostPath` mounts for music and long-form roots, both read-only
|
||||
- resource requests/limits, non-root security context, probes on `/health`
|
||||
- optional `nodeSelector`, `tolerations` and `affinity`
|
||||
|
||||
The secret is not created by the chart. Create it from the Vault-managed file:
|
||||
The registry is private, so the cluster needs an image pull secret, and the users
|
||||
secret must contain the Vault-managed file. `scripts/release.sh --deploy` creates
|
||||
both from the local `~/.docker/config.json` and `config/users.yaml`, then runs
|
||||
`helm upgrade --install`:
|
||||
|
||||
```bash
|
||||
docker login gitea.tap-tap.win
|
||||
scripts/release.sh --tag latest --deploy
|
||||
```
|
||||
|
||||
To deploy by hand:
|
||||
|
||||
```bash
|
||||
kubectl create namespace musicmanager
|
||||
|
||||
kubectl -n musicmanager create secret generic musicmanager-users \
|
||||
--from-file=users.yaml=config/users.yaml
|
||||
|
||||
kubectl -n musicmanager create secret generic musicmanager-registry \
|
||||
--type=kubernetes.io/dockerconfigjson \
|
||||
--from-file=.dockerconfigjson="$HOME/.docker/config.json"
|
||||
|
||||
helm upgrade --install musicmanager charts/musicmanager \
|
||||
--namespace musicmanager \
|
||||
--set image.tag=dev \
|
||||
--set users.existingSecret=musicmanager-users
|
||||
--set image.tag=latest \
|
||||
--set users.existingSecret=musicmanager-users \
|
||||
--set imagePullSecrets[0].name=musicmanager-registry
|
||||
```
|
||||
|
||||
Pin a specific build with `--set image.tag=sha-<commit>`; CI publishes that tag for
|
||||
every push to `main`.
|
||||
|
||||
Adjust `library.folders`, `media.music.hostPath` and `media.longform.hostPath` for
|
||||
the cluster. Every schedulable node must expose the same host paths; the chart
|
||||
deliberately does not pin the pod to a node.
|
||||
deliberately does not pin the pod to a node. The `/data` PVC must be writable by
|
||||
UID 10001 (the chart sets `fsGroup: 10001`).
|
||||
|
||||
The server exits at startup if a configured root path is missing or unreadable, so
|
||||
the pod will not pass its readiness probe in that case.
|
||||
|
||||
Reference in new issue
Block a user