[
https://issues.apache.org/jira/browse/FLINK-26894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513837#comment-17513837
]
Gyula Fora commented on FLINK-26894:
------------------------------------
I agree with the SPI part that would be a good way to load validator classes.
I don't think we can use libraries from the docker images. The operator only
gets the yaml and doesn't really have access to the contents of the Flink
docker images. So I think the custom validator artifacts must be added directly
to the flink-operator image somehow.
It would be awesome if somehow we could get it from the flink image but not
sure if thats realistic.
cc [~wangyang0918] [~matyas]
> 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)
