kubernetes-sigs / kubernetes-sigs/crdify

Property Validation: `exclusiveMaximum`

Open
#19 2 comments 0 reactions 2 assignees Claimed by @LoginovIlia View on GitHub
good first issue help wanted kind/feature priority/important-longterm triage/accepted
Dominant language
Go
Stars
47
Forks
22
PR merge metrics
No merged PRs in 30d

Description

The `exclusiveMaximum` constraint on a property enforces that the value is _up to but not including_ the maximum constraint.

Changing from an inclusive maximum to an exclusive maximum would be a breaking change as it shrinks the range of allowed values and thus breaks client/user expectations and may invalidate existing instances that use the inclusive maximum value.

Going from an exclusive maximum to an inclusive maximum would generally be OK as you would be expanding the range of allowed values and not be invalidating existing instances or client/user expectations of existing values that would work.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.