As Strimzi is nearing the 1.0.0 release, the Access operator should switch to the v1 API to maintain compatibility. Ideally, we want to do that before the 1.0.0 release. But it might not be possible due to how Fabric8 handles the custom resources and their versions.
It seems like we habe the following options:
- Use
GenericKubernetesResource and internally cast it to the Strimzi API class. But not sure if this is supported by the Operator SDK InformerEventSource.
- Wait for the Strimzi 1.0.0 release and use the 1.0.0's
api module. This would probably mean a simple change (just a dependency update). But it can happen only after 1.0.0 release.
As Strimzi is nearing the 1.0.0 release, the Access operator should switch to the
v1API to maintain compatibility. Ideally, we want to do that before the 1.0.0 release. But it might not be possible due to how Fabric8 handles the custom resources and their versions.It seems like we habe the following options:
GenericKubernetesResourceand internally cast it to the Strimzi API class. But not sure if this is supported by the Operator SDKInformerEventSource.apimodule. This would probably mean a simple change (just a dependency update). But it can happen only after 1.0.0 release.