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/05/10 14:01:00 UTC
[jira] [Updated] (FLINK-26955) Add CRD compatibility check
[ https://issues.apache.org/jira/browse/FLINK-26955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora updated FLINK-26955:
-------------------------------
Fix Version/s: kubernetes-operator-1.1.0
(was: kubernetes-operator-1.0.0)
> Add CRD compatibility check
> ---------------------------
>
> Key: FLINK-26955
> URL: https://issues.apache.org/jira/browse/FLINK-26955
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
> Fix For: kubernetes-operator-1.1.0
>
>
> Now with a preview release (almost) out. We should make sure that we do not introduce non-backward compatible changes to the CRD as it can cause serious issues on Kubernetes clusters.
> There are 2 aspects to this:
> 1. If we introduce a breaking change to already released CRDs we need to bump the version of the CRD (this is not the scope of the ticket)
> 2. We should add a verification step in the build ensuring that the CRD changes are compatible
> We should try to find a tool that can compare the openAPIV3Schema of the two CRDs and verify compatibility and integrate this into the maven build.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)