ObjectBucketClaim with maxObjects incorrectly set to an integer will break the operator & prevent all new object creation about rook HOT 3 OPEN

@mitchese can you provide a string in the maxObjects and re-start the rook operator pod?

from rook.

Of course the string works. If you adjust the OBC to have maxObjects: "100" then on the next start of the operator the crashloop goes away and the operator runs.

The problem is, a random user of our cluster can create a broken yaml which is accepted (/not validated) by the CRD. This then kills the operator on the next restart and breaks all operator operations for all users until we discover/fix it. Worse, the log doesn't mention which OBC has this problem so our search is manual to find which namespace and OBC has this integer. And our inital search today was difficult because the offending OBC was created weeks ago, and the operator was only restarted recently.

We've got a gatekeeper rule in place as a bandaid for now, but this should be gracefully handled such that it doesn't fail.

from rook.

Sure we should use the x-validation for the object-bucket CRD

from rook.