operator-framework artifact contains demo CRDs that are applied automatically

[fernanfs]

Bug Report

The operator-framework jar contains seemingly all demo CRDs of the java operator sdk. These can be found in META-INF/fabric8/*.yml. As these CRDs are on the default search path when using the crd auto-apply of the spring boot integration. Due to this, all CRDs will be uploaded to Kubernetes.

What did you do?

The project is a simple spring boot based operator using version 5.0.4 of the operator framework and version 6.0.1 of the spring boot integration:

    <dependency>
      <groupId>io.javaoperatorsdk</groupId>
      <artifactId>operator-framework-spring-boot-starter</artifactId>
      <version>6.0.1</version>
    </dependency>
    <dependency>
      <groupId>io.javaoperatorsdk</groupId>
      <artifactId>operator-framework-spring-boot-starter-test</artifactId>
      <version>6.0.1</version>
      <scope>test</scope>
    </dependency>

What did you expect to see?

Only the CRD of my application should be applied.

What did you see instead? Under which circumstances?

During startup I see a long list of other CRDs to be applied (the example CRDs).

Possible Solution

There doesn't seem to be a good reason to have the example CRDs included in the operator-framework artifact. These should be removed.

[csviri]

thx @fernanfs , yes those CRDs should not be there. Attached related PR.