azure CAS: add reviewers

[jackfrancis]

What type of PR is this?

What this PR does / why we need it:

This PR adds reviewers to the Azure CAS provider based on demonstrated participation in the project. See:

• https://github.com/kubernetes/autoscaler/pulls?q=is%3Aclosed+is%3Apr+label%3Aarea%2Fprovider%2Fazure+

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[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.

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

[jackfrancis]

Thank you @nojnhuh @rakechill @charliedmcb @aagusuab !!!

[jackfrancis]

/assign @tallaxes

[jackfrancis]

ping @tallaxes

[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

[jackfrancis]

/remove-lifecycle stale

[tallaxes]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis, tallaxes

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:

• cluster-autoscaler/cloudprovider/azure/OWNERS [jackfrancis,tallaxes]

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

[Shubham82]

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.

• charliedmcb

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

• aagusuab

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

• rakechill

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

Hi, @jackfrancis this PR is not merged because the members you added for reviewers are not the members in the k8s org, It will be good if they can become members in k8s org so they can review and give lgtm to the PR easily otherwise lgtm label will not work for them.

[Shubham82]

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.

• charliedmcb

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

• aagusuab

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

• rakechill

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

Hi, @jackfrancis this PR is not merged because the members you added for reviewers are not the members in the k8s org, It will be good if they can become members in k8s org so they can review and give lgtm to the PR easily otherwise lgtm label will not work for them.

Hi @jackfrancis, any update on this?

[Shubham82]

/hold
unhold it, once members (in the owners file) become members in k8s org.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten