I don't see a concern with this either. The only thing I thought about is that the operator has a dependency to Flink .. but since the JVM is backwards compatible, we will be able to consume that Java 8 or Java 11 dependency with a JDK 17. There are obviously Java language, JVM performance and vendor support benefits to using a newer JVM, so I'm +1 on this.
On Wed, May 28, 2025 at 5:25 AM Ryan van Huuksloot <ryan.vanhuuksl...@shopify.com.invalid> wrote: > Hi Gyula, > > Thanks for the discussion. > > I have no immediate concerns with the proper documentation when releasing > 1.13.0. > > We have a custom build that we could beta test with prior to finalizing the > 1.13.0 release. > > Ryan van Huuksloot > Sr. Production Engineer | Streaming Platform > [image: Shopify] > <https://www.shopify.com/?utm_medium=salessignatures&utm_source=hs_email> > > > On Tue, May 27, 2025 at 4:33 AM Gyula Fóra <gyula.f...@gmail.com> wrote: > > > Hi all, > > > > Attila has been working on upgrading the JOSDK and Fabric8 versions for > the > > Kubernetes operator. > > > > The latest version (JOSDK 5.1.0) is no longer compatible with Java 11, so > > we would like to upgrade the operator runtime to Java 17. > > > > The operator runtime version will not affect compatibility with Flink > jobs > > running other java versions however operator users may need to update > their > > operator base image if they use custom builds to use at least java 17. > > > > We suggest upgrading this for the 1.13.0 operator release. We will > include > > relevant documentation and call this out in the release notes. > > > > Any concerns? > > > > Cheers, > > Gyula > > >
