The centrepiece is the secret inventory: the four OnePasswordItem CRs carry only item paths, while the fields each item must contain are decided in the deployment. The notes list them per item — including the eight OIDC fields nobody would guess — because a missing field does not fail the install, it starts the container with an empty variable and misbehaves later. The warnings are the ones this chart earns: - Sign-in is OIDC-only. The chart sets OIDC_DISABLE_LOCAL_AUTH, so a wrong OIDC item locks everyone out with no local account to fall back on. - A wrong ingress.domain never becomes Ready: the server answers 403 to any unknown Host header, the probes send that domain, and the log shows plain 403s rather than anything resembling a configuration error. - The first 2.x start rebuilds database indexes and may take minutes, so the notes print the actual startup budget and say a slow boot is not a hang. - The presence registry is keyed by pod hostname, so replicas do not scale. The startup budget is read through the null-safe probe helper, and the guacd sidecar and scaled-down states are reported only when they apply. Refs #43.
13 lines
293 B
YAML
13 lines
293 B
YAML
apiVersion: v2
|
|
name: patchmon
|
|
description: A Helm chart to deploy Patchmon on Kubernetes
|
|
icon: https://raw.githubusercontent.com/PatchMon/PatchMon/main/frontend/public/assets/logo_square_default.svg
|
|
|
|
type: application
|
|
|
|
version: 6.1.0+up2.1.3
|
|
appVersion: "2.1.3"
|
|
|
|
maintainers:
|
|
- name: jklein
|