Hi devs,
I'd like to start a discussion about maintainers for DockerHub repositories
under the *apache* namespace [1].
Currently, the Flink community maintains various repositories (flink,
flink-statefun, flink-statefun-playground, and flink-kubernetes-operator)
on DockerHub under the *apache* na
Forgot to mention that, we have also proposed to use one shared account and
limit its access to the PMC members, like what we do with the PyPI account.
Unfortunately, INFRA rejected this proposal [1].
Thank you~
Xintong Song
[1] https://issues.apache.org/jira/browse/INFRA-23208
On Thu, Apr 28
We could just stop releasing to apache/flink and only go for the
official-images route.
On 28/04/2022 07:43, Xintong Song wrote:
Forgot to mention that, we have also proposed to use one shared account and
limit its access to the PMC members, like what we do with the PyPI account.
Unfortunately,
I'm overall against only releasing to official-images.
We started releasing to apache/flink, in addition to the official-image, in
1.12.0. That was because releasing the official-image needs approval from
the DockerHub folks, which is not under control of the Flink community. For
1.12.0 there were
I still think that's mostly a process issue.
Of course we can be blind-sided if we do the QA for a release artifact
after the release has been finalized.
But that's a clearly broken process from the get-go.
At the very least we should already open a PR when the RC is created to
get earlier fee
I agree with you that doing QA for the image after the release has been
finalized doesn't feel right. IIUR, that is mostly because official image
PR needs 1) the binary release being deployed and propagated and 2) the
corresponding git commit being specified. I'm not completely sure about
this. May
The flink-kubernetes-operator project is only published
via apache/flink-kubernetes-operator on docker hub and github packages.
We do not find the obvious advantages by using docker hub official images.
Best,
Yang
Xintong Song 于2022年4月28日周四 19:27写道：
> I agree with you that doing QA for the imag
One advantage is that the images are periodically rebuilt to get
security fixes.
The operator is a different story anyway because it is AFAIK only
supposed to be used via docker
(i.e., no standalone mode), which alleviates concerns about keeping the
logic within the image
to a minimum (which
It seems to me we at least don't have a consensus on dropping the use of
apache namespace, which means we need to decide on a list of maintainers
anyway. So maybe we can get the discussion back to the maintainers. We may
continue the official-image vs. apache-namespace in a separate thread if
neces
Hi everyone,
thanks for starting this discussion Xintong. I would volunteer as a
maintainer of the flink-statefun Docker repository if you need one.
Cheers,
Till
On Fri, May 6, 2022 at 6:22 AM Xintong Song wrote:
> It seems to me we at least don't have a consensus on dropping the use of
> apac
Hi Xintong,
it is a pity that we can only have 5 maintainers. Every (patch) release of
flink, flink-statefun, the flink-kubernetes-operator requires a maintainer
to publish the image then, if I am not mistaken. As its mostly different
groups managing the sub-projects, this is quite the bottleneck.
@Till,
Thanks for volunteering.
@Konstantin,
>From my experience, the effort that requires DockerHub access in the main
project release process is quite limited. I helped Yun Gao on releasing the
1.15.0 images, and what I did was just check out the `flink-docker` repo
and run the release script,
Hi team,
I volunteer for the flink-kubernetes-operator repo.
On Fri, May 6, 2022 at 1:42 PM Xintong Song wrote:
> @Till,
>
> Thanks for volunteering.
>
> @Konstantin,
>
> From my experience, the effort that requires DockerHub access in the main
> project release process is quite limited. I help
Thanks for volunteering, Marton.
Since the discussion has been open for quite long and no one else is
volunteering, I'll reply to the INFRA with the list of 4 maintainers
(Xintong, Jinsong, Till, Marton).
Thank you~
Xintong Song
On Sat, May 7, 2022 at 3:15 PM Márton Balassi
wrote:
> Hi team
14 matches
Mail list logo
