Closed spenczar closed 2 years ago
This sort of hacks in a fix for #5. It permits a user to define their StrimziSchemaRegistry resource with a specific strimzi API version, like this:
apiVersion: roundtable.lsst.codes/v1beta1 kind: StrimziSchemaRegistry metadata: name: confluent-schema-registry spec: strimzi-version: v1beta2
It's not an elegant fix, but this will be backwards compatible and seems to work.
This looks like a reasonable solution :+1:
This sort of hacks in a fix for #5. It permits a user to define their StrimziSchemaRegistry resource with a specific strimzi API version, like this:
It's not an elegant fix, but this will be backwards compatible and seems to work.