[ 
https://issues.apache.org/jira/browse/FLINK-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aitozi updated FLINK-20411:
---------------------------
    Description: 
Now we support user to set annotations by these config, the format is 
"k1:v1,k2:v2".
 # kubernetes.rest-service.annotations 
 # kubernetes.jobmanager.annotations
 # kubernetes.taskmanager.annotations

But the annotation may be more complex structure like 
"k1:\{"a1":"v1","a2":"v2"},k2:\{"a1":"v1","a2":"v2"}", It can not be parsed. 

Shall we support annotation and labels just like the environment variables use 
a prefix split mechanism, like :
 # kubernetes.rest-service.annotation.k1="\{"a1":"v1","a2":"v2"}"

By this we can set some default cluster annotations and labels and no need to 
worry about overridden by user config.

 

 

  was:
Now we support user to set annotations by these config, the format is 
"k1:v1,k2:v2".
 # kubernetes.rest-service.annotations 
 # kubernetes.jobmanager.annotations
 # kubernetes.taskmanager.annotations

But the annotation may be more complex structure like 
"k1:\{"a1":"v1","a2":"v2"},k2:\{"a1":"v1","a2":"v2"}", It can not be parsed. 

Shall we support annotation and labels just like the environment variables use 
a prefix split mechanism, like :
 # kubernetes.rest-service.annotation.k1="\{"a1":"v1","a2":"v2"}"

 

By this we can also set some default cluster annotations and labels and no need 
to worry about overridden by user config.

 

 


> The annotation config do not support complex structure
> ------------------------------------------------------
>
>                 Key: FLINK-20411
>                 URL: https://issues.apache.org/jira/browse/FLINK-20411
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.11.2
>            Reporter: Aitozi
>            Priority: Minor
>
> Now we support user to set annotations by these config, the format is 
> "k1:v1,k2:v2".
>  # kubernetes.rest-service.annotations 
>  # kubernetes.jobmanager.annotations
>  # kubernetes.taskmanager.annotations
> But the annotation may be more complex structure like 
> "k1:\{"a1":"v1","a2":"v2"},k2:\{"a1":"v1","a2":"v2"}", It can not be parsed. 
> Shall we support annotation and labels just like the environment variables 
> use a prefix split mechanism, like :
>  # kubernetes.rest-service.annotation.k1="\{"a1":"v1","a2":"v2"}"
> By this we can set some default cluster annotations and labels and no need to 
> worry about overridden by user config.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to