Property Validation: `not`

[everettraven]

The not constraint on a property means that its value cannot match the subschema.

As of writing this, my take on this is:

• Adding/changing not is more restrictive and breaking.
• Removing not is less restrictive and OK.

[stas17]

@everettraven I wanted to ask: is there any consideration allowing multiple types (e.g., type: ["string", "number"]) in CRD validation schemas?

[stas17]

/assign

[everettraven]

@everettraven I wanted to ask: is there any consideration allowing multiple types (e.g., type: ["string", "number"]) in CRD validation schemas?

@stas17 I don't think the type constraint allows a slice of types but I do think it is possible to allow multiple allowed types by using the anyOf or oneOf constraints.

[Sammyjroberts]

/assign