[
https://issues.apache.org/jira/browse/FLINK-27688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539047#comment-17539047
]
Gyula Fora commented on FLINK-27688:
------------------------------------
I think we should keep the Kubernetes event mechanism and add an
FlinkOperatorEventListener interface which could expose callbacks on status
changes and event triggers.
> Pluggable backend for EventUtils
> --------------------------------
>
> Key: FLINK-27688
> URL: https://issues.apache.org/jira/browse/FLINK-27688
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Márton Balassi
> Assignee: Gyula Fora
> Priority: Major
> Fix For: kubernetes-operator-1.1.0
>
>
> Currently the
> [EventUtils|https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/utils/EventUtils.java]
> utility that we use to publish events for the operator has an implementation
> that is tightly coupled with the [Kubernetes
> Events|https://www.containiq.com/post/kubernetes-events] mechanism.
> I suggest to enhance this with a pluggable event interface, which could be
> implemented by our users to support their event messaging system of choice.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
