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

Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/03/29 03:29:00 UTC

[jira] [Commented] (FLINK-26894) Support custom validator implementations

    [ https://issues.apache.org/jira/browse/FLINK-26894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513780#comment-17513780 ] 

Nicholas Jiang commented on FLINK-26894:
----------------------------------------

About specifying custom validator implementations, we could allow users to add the custom implementations by SPI. Thus FlinkOperator loads all the implementations of validator to validate the the operator configuration. 
About exposion for adding extra libraries, we could require users to add the libraries to the 'flink-artifact' of the 'flink-main-container'.
[~gyfora], WDYT?

> Support custom validator implementations
> ----------------------------------------
>
>                 Key: FLINK-26894
>                 URL: https://issues.apache.org/jira/browse/FLINK-26894
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>             Fix For: kubernetes-operator-1.0.0
>
>
> We should allow users to specify custom validator implementations through the operator configuration. This can be very useful in production environments to implement custom validation logic that is specific to certain envs.
> We should also expose a simple way for users to add extra libraries when deploying the operator



--
This message was sent by Atlassian Jira
(v8.20.1#820001)