[
https://issues.apache.org/jira/browse/FLINK-29108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17596903#comment-17596903
]
Gyula Fora commented on FLINK-29108:
------------------------------------
I understand that this is an important feature for you. But putting something
like this into the CRD and adding it to the operator logic is not necessarily
something we should do for a deprecated feature.
If you manage to convince the community to "undeprecate" it and support it
forward then it's a slightly different situation but even then it might be an
overkill to bake the support into the operator.
What I suggest as a first step and a middle-ground is to add some plugin
mechanism to be able to extend the core opertaor logic in a way that something
like this can be implemented. We can then have this as a reference
implementation / example in the repo.
> Kubernetes operator: Support queryable state
> --------------------------------------------
>
> Key: FLINK-29108
> URL: https://issues.apache.org/jira/browse/FLINK-29108
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Ron Crocker
> Priority: Minor
>
> Enable the kubernetes operator to deploy jobs where queryable state is
> desired.
> When queryable state is desired, the operator should configure the deployed
> job with
> # The deployed job has {{queryable-state.enabled:}} {{true}} applied to it.
> # Configure the Queryable State proxy and Queryable State server (via the
> {{queryable-state.proxy}} and {{queryable-state.server}} configuration
> sections respectively). If these sections aren't provided, then the default
> configuration is used.
> The operator will need to create a Kubernetes service fronting the Task
> Managers {{QueryableStateClientProxy}} port (as configured by the above).
> Tearing down the job also tears down the service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
