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 them in your K8s operator. [1]. https://github.com/wangyang0918/flink-native-k8s-operator/blob/master/deploy/crd.yaml [2]. https://github.com/wangyang0918/flink-native-k8s-operator/blob/master/deploy/cr.yaml Best, Yang gaurav kulkarni <[email protected]> 于2021年4月20日周二 上午8:57写道： > 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 >
