+1 for increasing the visibility of flink-kubernetes-operator. Best, Yang
Thomas Weise <t...@apache.org> 于2022年10月13日周四 07:49写道: > +1 > > > On Wed, Oct 12, 2022 at 5:03 PM Martijn Visser <martijnvis...@apache.org> > wrote: > > > +1 from my end to include the operator in the related Kubernetes sections > > of the Flink docs > > > > On Wed, Oct 12, 2022 at 5:31 PM Chesnay Schepler <ches...@apache.org> > > wrote: > > > > > I don't see a reason for why we shouldn't at least mention the operator > > > in the kubernetes docs. > > > > > > On 12/10/2022 16:25, Gyula Fóra wrote: > > > > Hi Devs! > > > > > > > > I would like to start a discussion about referencing the Flink > > Kubernetes > > > > Operator directly from the Flink Kubernetes deployment documentation. > > > > > > > > Currently the Flink deployment/resource provider docs provide some > > > > information for the Standalone and Native Kubernetes integration > > without > > > > any reference to the operator. > > > > > > > > I think we reached a point with the operator where we should provide > a > > > bit > > > > more visibility and value to the users by directly proposing to use > the > > > > operator when considering Flink on Kubernetes. We should definitely > > keep > > > > the current docs but make the point that for most users the easiest > way > > > to > > > > use Flink on Kubernetes is probably through the operator (where they > > can > > > > now benefit from both standalone and native integration under the > > hood). > > > > This should help us avoid cases where a new user completely misses > the > > > > existence of the operator when starting out based on the Flink docs. > > > > > > > > What do you think? > > > > > > > > Gyula > > > > > > > > > > > > >