Exactly.
I think most of the fields could be shared by standalone and native mode.
Best,
Yang
gaurav kulkarni 于2021年4月21日周三 上午10:17写道：
> Thanks a lot for the response, folks! I appreciate it. I plan to use
> native mode in future mostly for the resource management it plans to offer.
> Let me
Thanks a lot for the response, folks! I appreciate it. I plan to use native
mode in future mostly for the resource management it plans to offer. Let me go
through the links provided.
@Yang Wang "Since the CR is defined in yaml[2], native and standalone could
have some dedicated fields. And yo
Hi Gaurav,
I think the name "Native Kubernetes" is a bit misleading – this just means
that you can use the Flink CLI/ scripts to run Flink applications on
Kubernetes without using the Kubernetes APIs/ kubectl directly. What
features are you looking to use in the native mode?
I think it would be d
I think the compatibility depends on you. For example, you could have the
same
CustomResourceDefinition for standalone and native Flink applications. They
could
look like this[1].
Since the CR is defined in yaml[2], native and standalone could have some
dedicated fields.
And you could easily parse
Hi,
I plan to create a flink K8s operator which supports standalone mode, and and
switch to native mode sometime later. I was wondering what are some of the
approaches to ensure that CRD is compatible with both native and standalone
mode?
Thanks
