Skip to content
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

[Task]: Single dockerhub repository for Flink job server container #31631

Open
1 of 16 tasks
Abacn opened this issue Jun 18, 2024 · 1 comment
Open
1 of 16 tasks

[Task]: Single dockerhub repository for Flink job server container #31631

Abacn opened this issue Jun 18, 2024 · 1 comment

Comments

@Abacn
Copy link
Contributor

Abacn commented Jun 18, 2024

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

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@kennknowles
Copy link
Member

Pinging @je-ik and @thebozzcl explicitly here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants