Enable direct reconciliation of the v1beta1 types

[jaronoff97]

Component(s)

collector

Is your feature request related to a problem? Please describe.

The operator should add the v1alpha2 types to its known schemas

Describe the solution you'd like

Add it to the scheme

Describe alternatives you've considered

No response

Additional context

No response

[pavolloffay]

I have started looking into this:

• add conversion webhook
• include v1alpha2 CRD in the bundle and manifests
• add v1alpha2 to reconciliation

[pavolloffay]

Note when v1alpha2 is enabled we run into

The CustomResourceDefinition "opentelemetrycollectors.opentelemetry.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

In the past it was solved with #1981 (comment) to trim the CRD description.

This happens with kubectl apply as it stores the last version in the annotations that has a limited size. The problem does not occur with kubectl create|replace commands.

[pavolloffay]

The setting description size to 0 fixed the issue.

Notes:

• k get otelcol.v1alpha1.opentelemetry.io and k get otelcol.v1beta1.opentelemetry.io
• // +kubebuilder:unservedversion - not serve the version
• // +kubebuilder:storageversion - only a single version is storage version. When an object is written, it is stored at the version designated as the storage version at the time of the write

https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#previous-storage-versions