Add tomasaschan to kdp maintainers

[justinsb]

To support kubernetes-sigs/kubebuilder-declarative-pattern#417 and similar

tomasaschan is already in OWNERS as an approver

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: justinsb, tomasaschan
Once this PR has been reviewed and has the lgtm label, please assign jpbetz for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• config/kubernetes-sigs/sig-api-machinery/OWNERS

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

[tomasaschan]

/lgtm

[Priyankasaggu11929]

cc: @kubernetes/sig-api-machinery-leads for approve

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tomasaschan]

It makes me sad that stuff like this doesn't get attention. Not only because this is about me specifically, but the wording here is so ironic - the bot starts by explaining that k8s doesn't have enough contributors, but resolving this (which seems to me like it should be a very quick review) is literally a way to help mitigate that very problem.

[tomasaschan]

/remove-lifecycle stale

Ping @kubernetes/sig-api-machinery-leads

[k8s-ci-robot]

@tomasaschan: The label(s) /remove-label kind/api-change cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label kind/api-change

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-sigs/prow repository.

[k8s-ci-robot]

@tomasaschan: Those labels are not set on the issue: api-review

In response to this:

/remove-label api-review

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-sigs/prow repository.

[justinsb]

Hey @mrbobbytables - did I do something wrong when I opened the PR? Like @tomasaschan I am surprised that this did not effectively merge-on-green