Hey Camila Macedo, Maybe I am mistaken in exactly what this validation is for. I was under the impression it is to ensure two things, both the value type and limited range of values of a property in the CR spec matches what we expect. This is fantastic if it is, as I was looking for it from the start as it ensures an early failure of a CR instantiation rather than having to look through operator logs.

In my mind to validate this PR, I would want to test each field validation individually across the 3 CRDs. Without doing this, in my mind, it is not tested and we are hoping it just works. This is why I said it would take a number of hours or longer to fully verify this PR.