feat: Add support for Trino 451 (#609)

* feat: Add support for Trino 451

* changelog

* fix: JVM config

* fix tests

* increase keycloak resources

* fix truncate test

* fix hive examples db user credentials

* fix linter

---------

Co-authored-by: Malte Sander <malte.sander.it@gmail.com>

Author: sbernauer

CHANGELOG.md

@@ -7,6 +7,7 @@ All notable changes to this project will be documented in this file.
 ### Added
 
 - Support row filters and column masks in Rego rules ([#559]).
+- Support for version `451` ([#609]).
 
 ### Changed
 
@@ -18,9 +19,14 @@ All notable changes to this project will be documented in this file.
 - Processing of corrupted log events fixed; If errors occur, the error
   messages are added to the log event ([#598]).
 
+### Removed
+
+- Support for version `428` ([#609]).
+
 [#559]: https://github.com/stackabletech/trino-operator/pull/559
 [#573]: https://github.com/stackabletech/trino-operator/pull/573
 [#598]: https://github.com/stackabletech/trino-operator/pull/598
+[#609]: https://github.com/stackabletech/trino-operator/pull/609
 
 ## [24.3.0] - 2024-03-20
 

docs/modules/trino/examples/getting_started/code/trino.yaml

@@ -5,7 +5,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     catalogLabelSelector:
       matchLabels:

docs/modules/trino/examples/getting_started/code/trino.yaml.j2

@@ -5,7 +5,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     catalogLabelSelector:
       matchLabels:

docs/modules/trino/examples/usage-guide/opa-bundle-trino-cm-428.yaml

@@ -17,7 +17,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     catalogLabelSelector:
       matchLabels:

docs/modules/trino/examples/usage-guide/trino-insecure.yaml

@@ -17,7 +17,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     tls:
       internalSecretClass: trino-internal-tls # <1>

docs/modules/trino/examples/usage-guide/trino-secure-internal-tls.yaml

@@ -17,7 +17,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     tls:
       serverSecretClass: trino-tls # <1>

docs/modules/trino/examples/usage-guide/trino-secure-tls-only.yaml

@@ -17,7 +17,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     tls:
       serverSecretClass: trino-tls # <1>

docs/modules/trino/examples/usage-guide/trino-secure-tls.yaml

@@ -72,7 +72,7 @@ metadata:
   name: simple-trino
 spec:
   image:
-    productVersion: "442"
+    productVersion: "451"
   clusterConfig:
     catalogLabelSelector:
       matchLabels:

docs/modules/trino/pages/usage-guide/catalogs/index.adoc

@@ -15,7 +15,7 @@ The coordinator process will receive a `SIGTERM` signal when Kubernetes wants to
 After the graceful shutdown timeout runs out, and the process still didn't exit, Kubernetes will issue a `SIGKILL` signal.
 
 When a coordinator gets restarted, all currently running queries will fail and cannot be recovered after the restart process is finished.
-As of Trino version `442` this can not be prevented (e.g. by using multiple coordinators).
+As of Trino version `451` this can not be prevented (e.g. by using multiple coordinators).
 
 == Workers