[
https://issues.apache.org/jira/browse/FLINK-21126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781680#comment-17781680
]
Junrui Li commented on FLINK-21126:
-----------------------------------
Hi [~thw],
I would like to know if the current official FLINK k8s operator still relies on
the FLINK_PROPERTIES environment variable after the introduction of FLIP-212:
Introduce Flink Kubernetes Operator?
> Reconsider FLINK_PROPERTIES
> ---------------------------
>
> Key: FLINK-21126
> URL: https://issues.apache.org/jira/browse/FLINK-21126
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Scripts
> Reporter: Chesnay Schepler
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
> Fix For: 2.0.0
>
>
> The docker scripts support a {{FLINK_PROPERTIES}} environment variable that
> contains a multi-line string with config options, that is piped into the
> configuration.
> This variable is somewhat redundant, because docker users can also specify a
> list of dynamic properties when starting a container, and Kubernetes users
> are advised to use config maps instead.
> FLIP-161 might also re-introduce new ways to configure Flink via environment
> variables.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
