You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/12/12 21:15:00 UTC

[jira] [Updated] (FLINK-29655) Split Flink CRD from flink-kubernates-operator module

     [ https://issues.apache.org/jira/browse/FLINK-29655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matyas Orhidi updated FLINK-29655:
----------------------------------
    Issue Type: New Feature  (was: Improvement)

> Split Flink CRD from flink-kubernates-operator module
> -----------------------------------------------------
>
>                 Key: FLINK-29655
>                 URL: https://issues.apache.org/jira/browse/FLINK-29655
>             Project: Flink
>          Issue Type: New Feature
>          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)