Each time a new Flink version is supported, we need to create a new dockerhub repo prior to the release process, which involves Apache Infra approval.
Conventionally, a Dockerhub repository contains versioned image of different base platforms, for example, official python image https://hub.docker.com/_/python/tags has tags like "3.9.19-slim-bullseye", "3-alpine3.19"
We should be able to publish Flink job servers into single repository, saying, apache/beam_flink_job_server, and use tag like 2.99.0-flink1.99
This involves refactoring and it is good to start when adding support of the next flink version
What needs to happen?
Each time a new Flink version is supported, we need to create a new dockerhub repo prior to the release process, which involves Apache Infra approval.
Conventionally, a Dockerhub repository contains versioned image of different base platforms, for example, official python image https://hub.docker.com/_/python/tags has tags like "3.9.19-slim-bullseye", "3-alpine3.19"
We should be able to publish Flink job servers into single repository, saying, apache/beam_flink_job_server, and use tag like
2.99.0-flink1.99
This involves refactoring and it is good to start when adding support of the next flink version
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components