Bump postgres chart to latest release #391
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#391
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "bump-postgres-chart"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See discussion in #387
Upgrade notes to Chart v11.x and Postgres 14.x: https://docs.bitnami.com/kubernetes/infrastructure/postgresql/administration/upgrade/
The current version in Gitea is using
11.11.0-debian-10-r62
from 2021-04.Bumping the chart to the latest (v12.x) would use the image
15.2.0-debian-11-r14
which would be a jump from postgres 11 to postgres 15. There are no specific notes for the v12.x chart release, hence we might be able to just go to 12.x directly.There have been some param renamings which I've reflected in the README.
⚠️ BREAKING
Users have to migrate their Postgres DB by e.g. restoring a previously created database dump into a clean installation.
WIP: Bump postgres to latest 11.xto Bump postgres to latest 11.xBump postgres to latest 11.xto Bump postgres chart to latest releasec484f9cc6e
to99671dc065
db0b659a05
to7d638853a9
7d638853a9
to34ccce3d10
34ccce3d10
to5351cc68a8
5351cc68a8
to3e9c9b449a
3e9c9b449a
to17dda3d9ab
17dda3d9ab
todcc8ce1c3c
Chart.lock
must be updated, too. And we should mention that there is a proper way of updating PGSQL databases.@ -818,0 +822,4 @@
Please read the [Postgres Release Notes](https://www.postgresql.org/docs/release/) for version-specific changes.
With respect to `values.yml`, parameters `username`, `database` and `postgresPassword` have been regrouped under `auth` and slightly renamed.
`persistence` has also been regrouped under the `primary` key.
Please adjust your `values.yml` accordingly.
Two occurrences.
@ -93,3 +93,3 @@
{{- define "postgresql.dns" -}}
{{- printf "%s-postgresql.%s.svc.%s:%g" .Release.Name .Release.Namespace .Values.clusterDomain .Values.postgresql.global.postgresql.servicePort -}}
{{- printf "%s-postgresql.%s.svc.%s:%g" .Release.Name .Release.Namespace .Values.clusterDomain .Values.postgresql.global.postgresql.auth.servicePort -}}
I know it's a PR for bumping the postgres version and nothing more. Do you fancy adding some simple unittests that ensure the mapping in our
values.yaml
works with the one the dependent chart expects? It should help with future updates, detecting changes.We could/should but then probably for all chart deps? This might take a bit of work. Let's track it in #409. I think this should not block this PR for now.
@ -140,3 +139,3 @@
# className: nginx
className:
annotations: {}
annotations:
We should keep the empty array/object consistent with the other definitions. It's easier to read. (related to several changes)
Yeah sorry for this, hitting the auto-format one time and then continueing brings trouble 😆️
Adding "breaking" label as it is a major bump for the database chart.
Please see my comments below.
@ -9,2 +9,2 @@
repository: https://raw.githubusercontent.com/bitnami/charts/pre-2022/bitnami
version: 10.3.17
repository: oci://registry-1.docker.io/bitnamicharts
version: 12.2.1
Apologies for not testing it earlier. In the meantime the latest version is 12.2.6. I think we can update to that version - I've already used that newer version during my tests. 😉
@ -814,7 +814,15 @@ See [CONTRIBUTORS GUIDE](CONTRIBUTING.md) for details.
This section lists major and breaking changes of each Helm Chart version.
Please read them carefully to upgrade successfully.
### To 7.0.0
I think this removal is a mistake. It must be kept, since Chart version 7.0.0 got released and had the breaking change of bumping Gitea to 1.18.1 and gpg key setup. See https://gitea.com/gitea/helm-chart/src/tag/v7.0.0#to-7-0-0
@ -769,4 +767,0 @@
| `postgresql.enabled` | Enable PostgreSQL | `true` |
| `postgresql.global.postgresql.postgresqlDatabase` | PostgreSQL database (overrides postgresqlDatabase) | `gitea` |
| `postgresql.global.postgresql.postgresqlUsername` | PostgreSQL username (overrides postgresqlUsername) | `gitea` |
| `postgresql.global.postgresql.postgresqlPassword` | PostgreSQL admin password (overrides postgresqlPassword) | `gitea` |
I just realized: Our description for
postgresqlPassword
is wrong. It is not the admin password. Based on the previously used Chart version 10.3.17 this would've beenpostgresqlPostgresPassword
. What we configure instead is the actual additional user that is not the super-global admin of that instance. IMO, that's the desired state.On the other hand: With Chart version 12.2.1 the key
postgresql.global.postgresql.auth.postgresPassword
is the password of that super-global admin and we have to usepostgresql.global.postgresql.auth.password
instead.@ -814,7 +814,15 @@ See [CONTRIBUTORS GUIDE](CONTRIBUTING.md) for details.
This section lists major and breaking changes of each Helm Chart version.
Please read them carefully to upgrade successfully.
### To 7.0.0
The confusion came up as someone assumed we need to always issue a major release for every gitea minor update, even if there are not breaking changes for the chart.
To clear the confusion, it might help to remove the statement of "this update bumps gitea to 1.18.1" as this somehow covers the underlying breaking change of the GPG key feature.
In other README changelog notes we never mentioned the Gitea minor release, hence I guess we should keep it at chart-related breaking changes to avoid confusion?
I've went ahead and did so, let me know what you thinK!
@ -769,4 +767,0 @@
| `postgresql.enabled` | Enable PostgreSQL | `true` |
| `postgresql.global.postgresql.postgresqlDatabase` | PostgreSQL database (overrides postgresqlDatabase) | `gitea` |
| `postgresql.global.postgresql.postgresqlUsername` | PostgreSQL username (overrides postgresqlUsername) | `gitea` |
| `postgresql.global.postgresql.postgresqlPassword` | PostgreSQL admin password (overrides postgresqlPassword) | `gitea` |
Good catch!
postgresPassword
topassword
for DB user 17b9ce1e9bLGTM. I've fixed a similar port templating issue as I mentioned in #412 (comment) for MySQL.
Works for me how you proposed. 👍
This comment is related to #391 (comment).
b9f313b115
Great, merging and moving onwards!