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

Posted to dev@flink.apache.org by "Daren Wong (Jira)" <ji...@apache.org> on 2023/04/13 13:03:00 UTC

[jira] [Created] (FLINK-31794) Ignore unknown CRD fields

Daren Wong created FLINK-31794:
----------------------------------

             Summary: Ignore unknown CRD fields
                 Key: FLINK-31794
                 URL: https://issues.apache.org/jira/browse/FLINK-31794
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.4.0
            Reporter: Daren Wong
             Fix For: kubernetes-operator-1.4.0


Currently, Kubernetes Operator fails to create a CR (FlinkDeployment or FlinkSessionJob) if there is a new field in the CR that's not included in the CRD.

This change is to propose removing this restriction for FlinkSessionJobStatus, FlinkSessionJobSpec, FlinkDeploymentStatus, FlinkDeploymentSpec by adding class-level annotation `{color:#bbb529}@JsonIgnoreProperties{color}(ignoreUnknown = {color:#cc7832}true{color})`.

 

This means that any new fields in CR will be ignored if it's not registered in CRD preventing failures to create the CR. This helps users who need to deploy CRD and Kubernetes Operator separately to ensure backward compatibility.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)