Add apelisse as approver to pkg/validation

[apelisse]

@liggitt Jordan, how do you feel about that?

[liggitt]

+1 on adding to reviewers list

For approvers, there isn't a ton of action in this subtree to get signal on historical reviews. It looks like the PRs to this package you've been a reviewer/author on have been:

• Add direct conversion from Gnostic v2 types to spec.Swagger #283
  • there were a decent number of edge cases, error paths, and test coverage updates needed
• openapiv2 experimental json unmarshaler #319
  • minor comment to minimize exposed API surface
• fix json unmarshal bug when extension used with Responses #320
  • minor missed error case
• Use "jsonv2"/go-json-experimental to marshal OpenAPI v2 #325
  • some notable behavior differences were introduced I would have expected to be noticed and highlighted or handled already
• Fix minor bug not deserializing a full-value in Paths#UnmarshalNextJSON #331
  • no substantive additions to your changes

Since stuff under here is API-facing (both in the serialized fields and in the behavior of the CRD validators), I'd look for a track record of you raising and driving to resolution compatibility implications of changes in reviews or changes you author.

[apelisse]

Updated

[liggitt]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: apelisse, liggitt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/validation/OWNERS [liggitt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment