You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/04/03 06:14:00 UTC

[jira] [Created] (FLINK-27029) DeploymentValidator should take default flink config into account during validation

Gyula Fora created FLINK-27029:
----------------------------------

             Summary: 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
             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.1#820001)