[
https://issues.apache.org/jira/browse/FLINK-29655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618949#comment-17618949
]
Márton Balassi commented on FLINK-29655:
----------------------------------------
Makes sense, this way you could also make the dependencies of the module quite
slim. Thanks.
> Split Flink CRD from flink-kubernates-operator module
> -----------------------------------------------------
>
> Key: FLINK-29655
> URL: https://issues.apache.org/jira/browse/FLINK-29655
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Minor
>
> To launch a flink job that managed by flink operator, it is required to
> introduce Flink CRD in backend service as dependency to create CR. In current
> model, all of the flink libs will be introduced to service. But actually
> what is required are model classes in the package in
> org.apache.flink.kubernetes.operator.crd.
> It will be user friendly to split org.apache.flink.kubernetes.operator.crd to
> a separate module as flink-kubernetes-crd.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
