CRD Version v1alpha2

[jenniferubah]

With the recent changes to RHDH plugins, we are now enabling the notifications, notifications-backend and notificatinemail plugins and signals/signal backends plugins by default. Hence no longer allowing the admin to configure these values via the CR/CRD. As this is a breaking change, we introduce the v1alpha2 version of the CRD, remove these values from the CRD and values.yaml files. We also added the new custom plugins orchestrator.

• Updated rhdh-operator manifest using this example

[pkliczewski]

@jordigilh please rereview this PR

[jianrongzhang89]

@jenniferubah @pkliczewski @masayag @jordigilh why are we introducing version v1alpha2? Will it replace v1aplah1, or both version will co-exist? Do we have customers who already use v1alpha1, and if so how do they migrate to v1alpha2? Thanks.

[jordigilh]

@jenniferubah @pkliczewski @masayag @jordigilh why are we introducing version v1alpha2? Will it replace v1aplah1, or both version will co-exist? Do we have customers who already use v1alpha1, and if so how do they migrate to v1alpha2? Thanks.

As discussed internally, we have agreed to raise the version due to the changes introduced here.

[jianrongzhang89]

@jenniferubah @pkliczewski @masayag @jordigilh why are we introducing version v1alpha2? Will it replace v1aplah1, or both version will co-exist? Do we have customers who already use v1alpha1, and if so how do they migrate to v1alpha2? Thanks.

As discussed internally, we have agreed to raise the version due to the changes introduced here.

Sounds good. Thank you @jordigilh

[pkliczewski]

@jordigilh do you think this change is ready? it is needed to release first RC build. it would be great to do it as soon as possible

[jordigilh]

/lgtm