[
https://issues.apache.org/jira/browse/FLINK-26214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511936#comment-17511936
]
Márton Balassi commented on FLINK-26214:
----------------------------------------
Hi team,
Thank you for gathering information on this topic. I suggest the following
based on the above docs:
# Publish "snapshot" docker artifact builds to ghcr.io. Do this only on the
main branch and if the CI passes, tag builds with commit_sha and a rolling
latest tag. This is a simplified version of airflow communities approach
# Publish release to Dockerhub as we do for other flink project docker
[artifacts|https://hub.docker.com/r/apache/flink].
Based on my experimentation so far to provide the best user experience to folks
who would like to reuse our GitHub workflows the best choice would be to name
the image
{noformat}
apache/flink-kubernetes-operator{noformat}
So exactly match the repository name, this enables permissions to work by
default without manual intervention. If we go down this path I would suggest to
use the same name for the helm chart.
I experienced the permission issue when trying to push to
mbalassi/flink-operator here:
[https://github.com/mbalassi/flink-kubernetes-operator/runs/5678808122?check_suite_focus=true]
This can be solved by manually enabling permission for each fork, but we can
fast-track this with conforming with the repo name.
What do you think?
> Publish Kubernetes operator to container registry
> -------------------------------------------------
>
> Key: FLINK-26214
> URL: https://issues.apache.org/jira/browse/FLINK-26214
> Project: Flink
> Issue Type: Sub-task
> Reporter: Zili Chen
> Assignee: Márton Balassi
> Priority: Major
>
> Created from
> https://github.com/apache/flink-kubernetes-operator/pull/4#issuecomment-1042717476.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
