Update provider-aws owners aliases

[DavidXU12345]

@nckturner and @wongma7 are no long in AWS. Remove them and add active owners (@DavidXU12345, @YangjinanHu and @samuhale) in AWS

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[k8s-ci-robot]

Hi @DavidXU12345. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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]

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes org. You can then trigger verification by writing /verify-owners in a comment.

• dankova22
  • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
• samuhale
  • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

[wongma7]

/ok-to-test

/lgtm

thanks

[wongma7]

/verify-owners

[Priyankasaggu11929]

/verify-owners

[Priyankasaggu11929]

/verify-owners

[Priyankasaggu11929]

Both @dankova22 and @samuhale are existing Kubernetes org members.

org/config/kubernetes-sigs/org.yaml

Line 757 in c12e9c6

- samuhale

org/config/kubernetes-sigs/org.yaml

Line 207 in c12e9c6

- dankova22

@kubernetes/owners, do you know what is wrong in the changes? Thanks!

[Priyankasaggu11929]

Oh, I think it actually requires the kubernetes github org membership.

@dankova22, @samuhale, could you please create a PR to add yourself to kubernetes org as well? Thanks!

[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

[palnabarun]

@DavidXU12345 could you please update the PR?

/remove-lifecycle stale

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes org. You can then trigger verification by writing /verify-owners in a comment.

• samuhale
  • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

[DavidXU12345]

@palnabarun
I have updated the PR, could you help to merge? thanks