[ https://issues.apache.org/jira/browse/FLINK-31794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-31794: ----------------------------------- Labels: pull-request-available (was: ) > 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 > Priority: Minor > Labels: pull-request-available > 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)