[
https://issues.apache.org/jira/browse/FLINK-38285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Mészáros updated FLINK-38285:
------------------------------------
Description:
Overriding or setting config options using environment variables would make the
operator more Kubernetes native since it is a common practice to have settings
propagated as env var (for Deployment object) in Kubernetes. Would also help to
override settings when running operator locally.
The only issue is how to encode flink config options as env vars, what I
propose is for names:
* dot would be replaced by by underscore: "." -> "_"
* - hypen by replaced by double underscore: "-" -> "__"
* to upper case
* prefixed by "FLINK_CONF_"
Thus "restart-strategy.failure-rate.delay" =>
"FLINK_CONF_RESTART_{_}STRATEGY_FAILURE{_}_RATE_DELAY"
Values can be simply in quotes like "1 m".
was:
Overriding or setting config options using environment variables would make the
operator more Kubernetes native since it is a common practice to have settings
propagated as env var (for Deployment object) in Kubernetes. Would also help to
override settings when running operator locally.
The only issue is how to encode flink config options as env vars, what I
propose is for names:
* dot would be replaced by by underscore: "." -> "_"
* - hypen by replaced by double underscore: "-" -> "__"
* to upper case
* prefixed by "FLINK_CONF_"
Thus "restart-strategy.failure-rate.delay" =>
"FLINK_CONF_RESTART_{_}STRATEGY_FAILURE{_}_RATE_DELAY"
Similarly to values:
"1 m" => "1_m"
> Allow to overrride config options with environment variables
> ------------------------------------------------------------
>
> Key: FLINK-38285
> URL: https://issues.apache.org/jira/browse/FLINK-38285
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Attila Mészáros
> Assignee: Attila Mészáros
> Priority: Major
>
> Overriding or setting config options using environment variables would make
> the operator more Kubernetes native since it is a common practice to have
> settings propagated as env var (for Deployment object) in Kubernetes. Would
> also help to override settings when running operator locally.
>
> The only issue is how to encode flink config options as env vars, what I
> propose is for names:
> * dot would be replaced by by underscore: "." -> "_"
> * - hypen by replaced by double underscore: "-" -> "__"
> * to upper case
> * prefixed by "FLINK_CONF_"
> Thus "restart-strategy.failure-rate.delay" =>
> "FLINK_CONF_RESTART_{_}STRATEGY_FAILURE{_}_RATE_DELAY"
> Values can be simply in quotes like "1 m".
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
