REQUEST: New membership for rawadhossain

[rawadhossain]

GitHub Username

@rawadhossain

Organization you are requesting membership in

kubernetes-sigs

Requirements

• I have reviewed the community membership guidelines
• I have enabled 2FA on my GitHub account
• I have subscribed to the kubernetes dev e-mail list
• I am actively contributing to 1 or more Kubernetes subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
• I have verified that my sponsors are from different member companies
• I have verified that my sponsors are a reviewer or an approver in at least one OWNERS file within one of the Kubernetes GitHub organizations (excluding the contributor-playground)
• SUGGESTED: Ensure your affiliation in gitdm is up to date (gitdm is used by devstats to track affiliation)
• SUGGESTED: Ensure your affiliation in openprofile.dev is up to date (used by LFX Insights to track affiliation, will replace gitdm in the future)
• SUGGESTED: I have taken the Inclusive Open Source Community Orientation course

Sponsor 1

@ajaysundark

Sponsor 2

@Karthik-K-N

List of contributions to the Kubernetes project

• PR authored
  feat: add node_readiness_build_info metric kubernetes-sigs/node-readiness-controller#406
  feat: add scrape-time metrics collector kubernetes-sigs/node-readiness-controller#398
  Add Prometheus metrics to readiness condition reporter kubernetes-sigs/node-readiness-controller#379
  Replace metric label literals with constants kubernetes-sigs/node-readiness-controller#353
  docs: add rule label docs for node_readiness_evaluation_duration_seconds kubernetes-sigs/node-readiness-controller#329
  test: add demo environment for testing kubernetes-sigs/node-readiness-controller#326
  Remove duplicate bootstrap duration observation in taint removal path kubernetes-sigs/node-readiness-controller#285
  fix: only append to appliedNodes after successful node evaluation kubernetes-sigs/node-readiness-controller#216
  Remove stale failedNodes entries for deleted nodes kubernetes-sigs/node-readiness-controller#204
  ci: fix lint issues for golangci-lint v2.12.1 kubernetes-sigs/node-readiness-controller#199
  feat: add blocked nodes metric to scrape-time collector kubernetes-sigs/node-readiness-controller#431
  Add reporter metrics to examples kubernetes-sigs/node-readiness-controller#419
  feat: add Fleet Overview Grafana dashboard kubernetes-sigs/node-readiness-controller#325
  fix: record conflict failures and fix missing status patch metric kubernetes-sigs/node-readiness-controller#320
  feat: Add bootstrap NRC duration metric kubernetes-sigs/node-readiness-controller#294
  feat: collector-based rule_matched_nodes and typed failure reasons kubernetes-sigs/node-readiness-controller#286
  feat: Add reconciliation retry observability metrics kubernetes-sigs/node-readiness-controller#288

• Issue opened
  [FEATURE] Scrape-Time Metrics Collector kubernetes-sigs/node-readiness-controller#397
  Nodes appear in both appliedNodes and failedNodes on evaluation failure kubernetes-sigs/node-readiness-controller#215
  Stale failedNodes entries remain after node deletion kubernetes-sigs/node-readiness-controller#203
  Bootstrap-only mode may reapply taint if bootstrap annotation fails kubernetes-sigs/node-readiness-controller#207
  [TRACKING] Update Existing Metrics kubernetes-sigs/node-readiness-controller#446

[AvineshTripathi]

+1

@rawadhossain is actively working on the node-readiness-controller and has significantly improved monitoring for the controller. Looking forward to collaborate more. Thanks!

[ajaysundark]

+1, thanks for your contributions, @rawadhossain !

[jasonbraganza]

@AvineshTripathi, please confirm work org is Sentinel One?

[AvineshTripathi]

yes, I contribute independent though

@AvineshTripathi, thank you.

Was asking because membership guidelines require that sponsors be from different organisations.

Sponsored by 2 reviewers. Note the following requirements for sponsors:
  * Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc.
  * Sponsors must be reviewers or approvers in at least one OWNERS file within one of the [Kubernetes GitHub organizations](https://github.com/kubernetes/community/blob/master/github-management#actively-used-github-organizations)
  * Sponsors must be from multiple member companies to demonstrate integration across community.

[jasonbraganza]

@AvineshTripathi, ooh apologies once again, but I also fail to find you in any OWNERS file. If I have missed any, could you point me to one?
If you aren’t in an OWNERS file, @rawadhossain will have to find another sponsor.

[Karthik-K-N]

+1
@rawadhossain have been actively contributing to Node-Readiness-Controller and doing great job. Thank you for all the amazing work you do. Happy to sponser

[jasonbraganza]

@rawadhossain, request you please update Sponsor 2 to @Karthik-K-N.
I’ll be able to process the request in my next run

[rawadhossain]

Hi @jasonbraganza, updated Sponsor 2 to @Karthik-K-N. Thanks.

[jasonbraganza]

/assign

Hello, hello, @rawadhossain 👋
Thank you for all your contributions 🙂

I’ve created PR #6582 to add you to the Kubernetes Org(s). Once that gets merged, you should receive a membership invite notification.

Welcome to @kubernetes! 🎉