Skip to content

chore: upgrade postgresql to 17.2 (chart 16.3.1) #642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 11 commits into
base: develop
Choose a base branch
from

Conversation

GreyXor
Copy link

@GreyXor GreyXor commented Oct 3, 2024

Description of the change

Update postgresql to 17.0 (chart version is 16.0)
close #641

Benefits

@provokateurin
Copy link
Member

Thanks, the version number of the Chart needs to be bumped as well. @jessebot @wrenix does this justify bumping the major version or would the minor version be enough?

@GreyXor
Copy link
Author

GreyXor commented Oct 3, 2024

Thanks, the version number of the Chart needs to be bumped as well. @jessebot @wrenix does this justify bumping the major version or would the minor version be enough?

Thanks, I'll update it when we know which version we need here 👍

@wrenix
Copy link
Collaborator

wrenix commented Oct 6, 2024

I have to take a look in the bitmani chart (if it make some migrates).
If not, i will bump a major version (like the bitmani chart too) and write a Changelog / Migration step.

PS: Private i wrote my own postgresql chart and use there the pgautoupgrade as init container (with PGAUTO_ONESHOT=yes) ...

@wrenix
Copy link
Collaborator

wrenix commented Oct 10, 2024

PS: Current PostgreSQL is not supported by Nextcloud (a Warnung appears): nextcloud/server#48495

@provokateurin
Copy link
Member

So better not merge it yet until any Nextcloud version officially supports it. It might just be alright, but better safe than sorry.

@provokateurin provokateurin marked this pull request as draft October 10, 2024 20:46
@jessebot
Copy link
Collaborator

Hoi! Yes, it should be a major update to the chart, as otherwise, it will attempt to upgrade a major version of the database if a user is using the bundled postgresql with this chart. I actually didn't know postgresql was supported by nextcloud at all :O Agree, if it is supported we should wait on this merge.

@GreyXor
Copy link
Author

GreyXor commented Nov 13, 2024

Nextcloud now officially support postgresql 17: nextcloud/server#49240
@provokateurin @wrenix
Thanks 👋

@provokateurin
Copy link
Member

That will only be in Nextcloud 31, so still not ready.

@GreyXor
Copy link
Author

GreyXor commented Nov 13, 2024

That will only be in Nextcloud 31, so still not ready.

In the meantime, waiting for 31. Does this PR seem ready to be merged? Or are there things to add/modify?

@wrenix
Copy link
Collaborator

wrenix commented Nov 15, 2024

nice do You like to make it merge ready? Maybe nextcloud/server@dea6bd7 would be in v30.0.3 ;)

Like to sign-of your commits (DCO check)

@provokateurin
Copy link
Member

would be in v30.0.3

No it won't, it is not on the stable30 branch which means it will be only in Nextcloud 31.

@GreyXor GreyXor changed the title chore: upgrade postgresql to 17.0 (chart 16.0.0) chore: upgrade postgresql to 17.0 (chart 16.2.0) Nov 19, 2024
@GreyXor GreyXor marked this pull request as ready for review November 19, 2024 07:51
@provokateurin
Copy link
Member

Can we please keep it as a draft until we have Nextcloud 31 support in the chart?

@GreyXor GreyXor marked this pull request as draft November 19, 2024 12:35
@GreyXor GreyXor changed the title chore: upgrade postgresql to 17.0 (chart 16.2.0) chore: upgrade postgresql to 17.0 (chart 16.3.1) Dec 13, 2024
@GreyXor GreyXor changed the title chore: upgrade postgresql to 17.0 (chart 16.3.1) chore: upgrade postgresql to 17.2 (chart 16.3.1) Dec 13, 2024
@wrenix wrenix changed the base branch from main to develop December 19, 2024 22:13
@wrenix wrenix force-pushed the develop branch 2 times, most recently from a5582d0 to 8667855 Compare December 19, 2024 22:27
@wrenix wrenix mentioned this pull request Dec 19, 2024
2 tasks
@wrenix wrenix force-pushed the develop branch 3 times, most recently from da98433 to b0d5e60 Compare December 19, 2024 22:51
@GreyXor GreyXor changed the base branch from develop to main January 12, 2025 19:11
@GreyXor GreyXor changed the base branch from main to develop January 12, 2025 19:12
dependabot bot and others added 10 commits February 25, 2025 09:34
Bumps [helm/kind-action](https://github.com/helm/kind-action) from 1.10.0 to 1.11.0.
- [Release notes](https://github.com/helm/kind-action/releases)
- [Commits](helm/kind-action@v1.10.0...v1.11.0)

---
updated-dependencies:
- dependency-name: helm/kind-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: GreyXor <[email protected]>
Signed-off-by: WrenIX <[email protected]>
Signed-off-by: GreyXor <[email protected]>
Signed-off-by: Dominic Giebert <[email protected]>
Signed-off-by: WrenIX <[email protected]>
Signed-off-by: GreyXor <[email protected]>
Bumps [helm/kind-action](https://github.com/helm/kind-action) from 1.11.0 to 1.12.0.
- [Release notes](https://github.com/helm/kind-action/releases)
- [Commits](helm/kind-action@v1.11.0...v1.12.0)

---
updated-dependencies:
- dependency-name: helm/kind-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: GreyXor <[email protected]>
Signed-off-by: wagoid <[email protected]>
Signed-off-by: Wagner Santos <[email protected]>
Signed-off-by: GreyXor <[email protected]>
Signed-off-by: Joshua Chapman <[email protected]>
Signed-off-by: GreyXor <[email protected]>
@GreyXor
Copy link
Author

GreyXor commented Feb 25, 2025

hi @provokateurin @wrenix
can I have a review ? nextcloud 31 will be soon be pushed to docker hub and then this helm can be updated to V7
Thanks

@GreyXor GreyXor marked this pull request as ready for review February 25, 2025 14:29
@wrenix wrenix force-pushed the develop branch 3 times, most recently from e2391c0 to de26dec Compare March 1, 2025 11:12
@wrenix
Copy link
Collaborator

wrenix commented Mar 6, 2025

Has somebody test a automatical migration? Maybe like:

postgresql:
  primary:
    initContainers:
      - name: upgrade
        image: "pgautoupgrade/pgautoupgrade:17-alpine"
        env:
          - name: "PGAUTO_ONESHOT"
            value: "yes"
        volumeMounts:
          - mountPath: "/bitnami/postgresql"
            name: "data"

@wrenix wrenix force-pushed the develop branch 2 times, most recently from abeb961 to aa0ac19 Compare March 17, 2025 19:41
@wrenix wrenix force-pushed the develop branch 2 times, most recently from a554746 to e9bad15 Compare May 18, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature: Update postgresql 17
7 participants