[ https://issues.apache.org/jira/browse/FLINK-37421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian updated FLINK-37421: --------------------------- Description: I don't see a way to add labels to the Deployment created by the FlinkDeployment. My organization has strict rules about deployment metadata which is preventing the flink operator from creating the deployment. Ideally the FlinkDeployment labels are copied directly to the Deployment it creates OR it provides another field in the spec. Labels on the deployment MUST be unique per FlinkDeployment. a global config via the [operator labels|https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/deployment/config/#kubernetes-jobmanager-labels] doesn't work for our use case. was: I don't see a way to add labels to the Deployment created by the FlinkDeployment. My organization has strict rules about deployment metadata which is preventing the flink operator from creating the deployment. Ideally the FlinkDeployment labels are copied directly to the Deployment it creates OR it provides another field in the spec. > [flink-operator][FlinkDeployment] Doesn't provide a mechanism to label the > deployment > ------------------------------------------------------------------------------------- > > Key: FLINK-37421 > URL: https://issues.apache.org/jira/browse/FLINK-37421 > Project: Flink > Issue Type: Bug > Reporter: Julian > Priority: Major > > I don't see a way to add labels to the Deployment created by the > FlinkDeployment. > My organization has strict rules about deployment metadata which is > preventing the flink operator from creating the deployment. > > Ideally the FlinkDeployment labels are copied directly to the Deployment it > creates OR it provides another field in the spec. > Labels on the deployment MUST be unique per FlinkDeployment. a global config > via the [operator > labels|https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/deployment/config/#kubernetes-jobmanager-labels] > doesn't work for our use case. -- This message was sent by Atlassian Jira (v8.20.10#820010)