[
https://issues.apache.org/jira/browse/FLINK-31857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31857:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Support pluginable observers mechanism
> --------------------------------------
>
> Key: FLINK-31857
> URL: https://issues.apache.org/jira/browse/FLINK-31857
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.5.0
> Reporter: Daren Wong
> Priority: Major
> Labels: pull-request-available, stale-major
>
> Currently, Kubernetes Operator uses AbstractFlinkResourceObserver to observe
> Flink Job state, cluster state, JM/TM state, etc and update Custom Resource:
> FlinkDeployment, FlinkSessionJob with the gathered info.
> This Jira is to introduce a Flink plugin to allow user to implement custom
> observer logic after the default observer logic is run.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
