Add 'kensipe' as reviewer

[kensipe]

I've provided a number of reviews and code including the bump to kube 1.16

Signed-off-by: Ken Sipe [email protected]

[kensipe]

/assign @DirectXMan12

[gerred]

/assign @gerred

[gerred]

I asked @kensipe to review #777, #776, and #773 to get current with the state of the repo before I approve this. He's been active in the past, but super excited for him to get back into the swing. Pending these steps, @alenkacz will you lgtm this? and then I'm happy to approve. Welcome aboard! ⛵️

[alenkacz]

👍

/lgtm

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kensipe
To complete the pull request process, please assign directxman12
You can assign the PR to them by writing /assign @directxman12 in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[kensipe]

rebased based on label

[gerred]

Thanks for your continued work on reviewing, and thanks for your stewardship of this ecosystem. As soon as #774 lands I will approve this PR.

[DirectXMan12]

I'm not necessarily against this, but I'd prefer to see a couple (doesn't need to be a ton, just a couple) more substantial PRs/contributions before marking as official reviewer (if I've missed or forgotten a few, feel free to let me know) -- see https://github.com/kubernetes-sigs/kubebuilder/blob/master/docs/CONTRIBUTING-ROLES.md#becoming-a-reviewer

[kensipe]

sure thing @DirectXMan12 I was out on PTO but back to active status

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.