-
Notifications
You must be signed in to change notification settings - Fork 213
Release Trino Gateway chart 1.16.0 #359
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
Conversation
|
@mosabua Trino Gateway 16 has been released, can you rebase? |
|
Rebased and pushed now .. lets see it turn green and then I will merge. |
|
There's an issue with starting up the PostgreSQL deployment. I've seen this in another PR recently. I need to investigate. Probably not related to the Gateway upgrade. |
|
Yeah .. I am checking what version of PostgreSQL we use in the project itself .. maybe upgrading helps .. do you think we are save to merge anyway? |
|
also remember some message about bitnami vs bitnami legacy |
|
Testing in the project uses postgres 17 .. so I think we should upgrade in the chart too |
|
Tests didn't run, so it's not safe to merge. We're using 17 in other tests and that fails to start too, even the images from the renamed bitnamilegacy repo. |
|
bitnami is stopping their whole public container and helm chart stuff it seems .. things moved to bitnamilegacy and we might need to use those for now and then also find alternative charts |
|
SIGH .. I will try to look later today |
|
Pretty sure we are falling victim to the bitnami deprecation - lots of details in bitnami/containers#83267 .. we might have to migrate to bitnamilegacy and archived containers for now and then find alternatives. Feel free to push commits in here or do another PR @nineinchnick |
|
Fixed now @nineinchnick .. WDYT? |
Depends on Trino Gateway 16 release - see trinodb/trino-gateway#643
CI will fail for now.