[ 
https://issues.apache.org/jira/browse/FLINK-26924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514534#comment-17514534
 ] 

Yang Wang commented on FLINK-26924:
-----------------------------------

+1 for the unified name "flink-kubernetes-operator", including the helm chart, 
docker images.

> Decide on operator docker image name
> ------------------------------------
>
>                 Key: FLINK-26924
>                 URL: https://issues.apache.org/jira/browse/FLINK-26924
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-0.1.0
>            Reporter: Márton Balassi
>            Assignee: Márton Balassi
>            Priority: Blocker
>
> 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|https://github.com/apache/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:
> {code:java}
> ghcr.io/apache/flink-operator:439bd41
> ghcr.io/apache/flink-operator:main{code}
> During the release process we plan to move the docker image to dockerhub 
> following the process established for 
> [Flink|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release#CreatingaFlinkRelease-PublishtheDockerfilesforthenewrelease].
> Currently the helm operator for the release candidate can be installed as 
> follows:
> {noformat}
> 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{noformat}
> 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?
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to