[
https://issues.apache.org/jira/browse/FLINK-29108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585531#comment-17585531
]
Ron Crocker commented on FLINK-29108:
-------------------------------------
[~masteryhx] In a word, yes.
There's two things in play:
# While its "reaching end of life," Queryable State remains a supported
capability in all of the Flink versions that the operator currently supports.
My company would like to use this Kubernetes operator to manage our Flink jobs,
and some of those jobs require Queryable State. We can't use this operator for
those jobs until it supports Queryable State for some of those jobs.
# I'm trying to rescue Queryable State from deprecation. In [my recent
presentation at Flink
Forward|[http://example.com|https://www.slideshare.net/FlinkForward/using-queryable-state-for-fun-and-profit]]
I made what I'd claim is a fairly strong argument for keeping queryable state
in the Flink feature set. ({_}TLDR: Using Flink Queryable State, I can save
>90% of the cost of the equivalent Redis-based solution{_})
I'm looking for allies in the fight to keep Queryable State alive.
> 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)
