[
https://issues.apache.org/jira/browse/FLINK-20632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255539#comment-17255539
]
Chesnay Schepler commented on FLINK-20632:
------------------------------------------
??maybe it is enough to postpone the release announcement until the Docker PR
is merged. That way we can first complete the Flink release, then update the
Docker image and lastly announce the release which makes it effectively
available to our users.
Would we have delayed the release for 2+ weeks because the docker images aren't
being released?
??Does our PMC has the authority to remove artifacts from the apache release
svn repository, say if we have not announced it???
Yes, we can do that.
??But maybe hosting the Flink docker images somewhere else will decouple our
release process from Dockerhub which already does the trick.
While it would solve the issue I do somewhat like going through the
official-images review process as an additional QA. We aren't _really_ familiar
with docker conventions, and the issue they pointed out does make sense after
all.
> Missing docker images for 1.12 release
> --------------------------------------
>
> Key: FLINK-20632
> URL: https://issues.apache.org/jira/browse/FLINK-20632
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.12.0
> Reporter: Piotr Gwiazda
> Priority: Critical
>
> Images for Flink 1.12 are missing in Docker hub
> https://hub.docker.com/_/flink. As a result Kubernetes deployment as in the
> documentation example is not working.
> https://ci.apache.org/projects/flink/flink-docs-release-1.12/deployment/resource-providers/native_kubernetes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
