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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/01/05 19:29:00 UTC

[jira] [Closed] (FLINK-29607) Simplify controller flow by introducing FlinkControllerContext

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

Gyula Fora closed FLINK-29607.
------------------------------
    Fix Version/s: kubernetes-operator-1.4.0
       Resolution: Fixed

merged to main 35604761eac2c75491811e731ffba540bc7e0363

> Simplify controller flow by introducing FlinkControllerContext
> --------------------------------------------------------------
>
>                 Key: FLINK-29607
>                 URL: https://issues.apache.org/jira/browse/FLINK-29607
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.4.0
>
>
> Currently contextual information such as observer/reconciler implementations, flink service, status recorder, generated configs are created/passed around in many pieces leading to a lot of overall code duplication in the system.
> We should introduce context object that capture these bits that could be reused across the controller flow to simplify the logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)