[FLINK-31794] Ignore unknown CRD fields

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.4.0
• Fix Version/s: kubernetes-operator-1.5.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Daren Wong
• Created: 13/Apr/23 13:02
• Updated: 20/Apr/23 13:28
• Resolved: 20/Apr/23 13:28

Description

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 `@JsonIgnoreProperties(ignoreUnknown = true)`.

 

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.

Issue Links

• links to: GitHub Pull Request #564