chore(trino): Update container image to 470 ahead of Stackable Release 25.3.0 #

[sbernauer]

Part of #964

• Add: 470

Tip

Please add the scheduled-for/2025-03 label, and add to the Stackable Engineering project.

Update tasks (trino)

Preview Give feedback

1. Update versions.py to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
2. Upload new version (see trino/*.sh scripts).
3. Update versions.py to the latest supported version of JVM (base and devel).
4. Update other dependencies if applicable (eg: jmx_exporter, opa_authorizer, storage_connector, etc).
5. Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
6. Update the version in demos. Add the PR(s) to the list below.

Update tasks (trino-cli)

Preview Give feedback

1. Update trino-cli/versions.py to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
2. Upload new version (see trino-cli/upload_new_trino_version.sh scripts).
3. Update versions.py to the latest supported version of JVM (base and devel).
4. Check other operators (getting_started / kuttl) for usage of the versions. Add the PR(s) to the list below.
5. Update the version in demos. Add the PR(s) to the list below.
6. Update the release note after the decision has been made'

Related Pull Requests

Preview Give feedback

1. feat(trino): Add 469 #993
   6 of 6
   release/25.3.0 +1
   
2. fix(trino): Restore trino-storage patches #996
   release/25.3.0 +1
   
3. feat(trino): Replace 469 with 470 #999
   3 of 4
   release/25.3.0 +1
   
4. https://github.com/stackabletech/decisions/issues/46
5. feat(stackable-operator/s3connection): Add region field defaulting to us-east-1 operator-rs#959
   3 of 9
   release/25.3.0 +1
   
6. chore(stackable-operator): Release 0.86.1 operator-rs#962
   release/25.3.0 +1
   
7. feat: Add region field to S3Connection and S3Bucket CRDs commons-operator#331
   3 of 12
   release/25.3.0 +1
   
8. feat: Add support for Trino 470 trino-operator#705
   0 of 15
   release/25.3.0 +1
   
9. Link to any other operator PRs (getting_started / kuttl)
10. feat(trino): Use 470 demos#149
    release/25.3.0 +1
    
11. docs: Mark Trino 455 as deprecated trino-operator#725
    release/25.3.0 +1
    
12. docs: Mark Trino 455 as deprecated trino-operator#726
    +0
    

Tip

Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been checked, the issue can be moved into Development: Done.

Acceptance

Preview Give feedback

1. Can build image (either locally, or in CI)
2. Kuttl smoke tests passes (either locally, or in CI)
3. Release notes written in a comment below
4. Applicable release-note label added to this issue

Testing instructions

# See the latest version at https://pypi.org/project/image-tools-stackabletech/
pip install image-tools-stackabletech==0.0.13

bake --product trino=x.y.z # where x.y.z is the new version added in this PR
bake --product trino-cli=x.y.z # where x.y.z is the new version added in this PR

kind load docker-image docker.stackable.tech/stackable/trino:x.y.z-stackable0.0.0-dev
kind load docker-image docker.stackable.tech/stackable/trino-cli:x.y.z-stackable0.0.0-dev

# Change directory into the trino-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.

[NickLarsenNZ]

Release Notes

trino: In vesion 470, S3 integration is done via the native S3 implementation (using the AWS SDK). Legacy S3 support (via Hadoop) has been disabled and will be removed in a future version of Trino. Consideration follow:

• SSL is always enabled and cannot be disabled.
• Client-side encryption is not supported. Server-side encryption (SSE) is the recommended alternative.
• Multipart (non-streaming) writes and upload are not supported.