[FLINK-26924] Decide on operator docker image name

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-0.1.0
• Fix Version/s: kubernetes-operator-0.1.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Márton Balassi
• Reporter: Márton Balassi
• Created: 30/Mar/22 08:04
• Updated: 31/Mar/22 09:18
• Resolved: 31/Mar/22 09:18

Description

For the sake of brevity when we started the Kubernetes Operator work we named the docker image and the helm chart simply flink-operator, while the git repository is named flink-kubernetes-operator.

Now closing in on our preview release it makes sense to reconsider this, it might be preferred to name all artifacts flink-kubernetes-operator for the sake of consistency.

Currently docker images of our builds are available in the GitHub Registry tagged with the short git commit hash and the last build of select branches is tagged with the branch name:

ghcr.io/apache/flink-operator:439bd41
ghcr.io/apache/flink-operator:main

During the release process we plan to move the docker image to dockerhub following the process established for Flink.

Currently the helm operator for the release candidate can be installed as follows:

helm repo add operator-rc2
https://dist.apache.org/repos/dist/dev/flink/flink-kubernetes-operator-0.1.0-rc2
helm install flink-operator operator-rc2/flink-operator

So the helm chart itself is called flink-operator, but to follow the name of the project it is packaged into flink-kubernetes-operator-<version>.tgz.

Do you prefer flink-operator for brevity or flink-kubernetes-operator for consistency?

 

Issue Links

• links to: GitHub Pull Request #138
• links to: GitHub Pull Request #140