Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| a964dc20a4 | |||
| e363c6594d |
@@ -187,15 +187,7 @@ spec:
|
|||||||
cpu: "50m"
|
cpu: "50m"
|
||||||
containers:
|
containers:
|
||||||
- name: umami
|
- name: umami
|
||||||
# NOTE: pinned to the exact image SHA the working 120d-old pod
|
image: ghcr.io/umami-software/umami:postgresql-v1.38.0
|
||||||
# is on. v1.38.0 (the latest postgresql-vX.Y.Z) tries to apply
|
|
||||||
# migration `02_add_event_data` which requires an `event` table
|
|
||||||
# that this DB doesn't have -- the DB schema is older than v1
|
|
||||||
# numbered migrations expect. Until we plan a proper migration
|
|
||||||
# (likely to umami v3.x, which is what the dashboard `→ 3.1`
|
|
||||||
# hint suggests), this stays SHA-pinned so Renovate doesn't
|
|
||||||
# touch it and pod restarts don't roll the version forward.
|
|
||||||
image: ghcr.io/umami-software/umami@sha256:28f263fe06f79ebffa5a6a6e9bd33b7a278e9342a88e0bdac812416c9f9e4361
|
|
||||||
ports:
|
ports:
|
||||||
- containerPort: 3000
|
- containerPort: 3000
|
||||||
env:
|
env:
|
||||||
|
|||||||
Reference in New Issue
Block a user