[
https://issues.apache.org/jira/browse/FLINK-29655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-29655.
------------------------------
Fix Version/s: kubernetes-operator-1.3.0
Resolution: Fixed
Merged to main:
a7e6f0c8dd08cecb26822731e058c003ac0fbee5
211a326a81c77c6d048e3d2ae9bb556f33ddd5aa
b4bef2b93c22cb603b832b31ede9c38d0b604970
> 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
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Minor
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.3.0
>
>
> 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)