Old Operators can not be added because of too strict validation

[ANeumann82]

Tried to add kafka operator 1.2.0 - It didn't work because the validator runs too many strict checks.

Additionally, when we add new validations in KUDO it might happen that existing entries in the index do not pass these new validations - the should still be added to the index on a rebuild.

So we need either a "skipValidation" or "validationLevel" or "kudoValidationVersion" that can execute the KUDO package validation with the correct KUDO version...

[nfnt]

Hmm, kitt has subcommands to distinguish between package validation and updating repositories. So validation can be skipped by only running the update subcommand. Or am I missing something here?

[ANeumann82]

Ah, ok... So that might work on a global level...

[nfnt]

As mentioned in #12, kitt needs a mechanism to support validation and possibly package creation for multiple versions of KUDO. This will allow it to manage repositories consisting of operator packages that may be incompatible with the latest version of KUDO but could still be used by older versions of KUDO.