[
https://issues.apache.org/jira/browse/FLINK-27029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-27029.
------------------------------
Resolution: Fixed
merged to main: 0c0ae05a4a2b73618e270f72a4a52a98fa4850c8
> DeploymentValidator should take default flink config into account during
> validation
> -----------------------------------------------------------------------------------
>
> Key: FLINK-27029
> URL: https://issues.apache.org/jira/browse/FLINK-27029
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available, starter
> Fix For: kubernetes-operator-1.0.0
>
>
> Currently the DefaultDeploymentValidator only takes the FlinkDeployment
> object into account.
> However in places where we validate the presence of config keys we should
> also consider the default flink config which might already provide default
> values for the required configs even if the deployment itself doesnt.
> We should make sure this works correctly both in the operator and the webhook
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
