THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
As this is a completely new standalone component, no migration will be necessary strictly speaking.
The user facing artifact is the CRD. Eventually we will need a compatibility story for the CRD, similar to the evolution of the Flink REST API.
- While experimental, we may introduce breaking changes to the current version of the CRD
- Once stable, the operator should support the previous version of CRD when breaking changes are made
- Supported Flink versions: operator should support n (TBD) Flink versions. Similar to a downstream project with Flink dependency.
- Above is relevant to reuse of Flink native client within operator. The Flink native integration itself must provide backward compatibility and compatible with lowest supported Flink version
Compatibility is to be seen and will depend on any changes required to the Flink Kubernetes integration.
...