REQUEST: New membership for Dasmat13

[Dasmat13]

GitHub Username

Dasmat13

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
• SUGGESTED: Ensure your affiliation in openprofile.dev is up to date
• SUGGESTED: I have taken the Inclusive Open Source Community Orientation course

Sponsor 1

@yankay

Sponsor 2

@mimowo

List of contributions to the Kubernetes project

I have been actively contributing across multiple kubernetes-sigs projects, mainly around controllers, admission/webhook validation, scheduling, reliability, and documentation.

Merged PRs

kubernetes-sigs/kueue

• Cherry pick 14020 to release 0.18 kubernetes-sigs/kueue#14559
• fix(multikueue): prevent establishWatch from blocking on timeout kubernetes-sigs/kueue#14020
• [release-0.18] fix(jobframework): fallback to annotation for prebuilt workload names exceeding 63 chars kubernetes-sigs/kueue#13661
• fix(jobframework): fallback to annotation for prebuilt workload names exceeding 63 chars kubernetes-sigs/kueue#13636
• fix(kueueviz): safely render error details and handle circular error … kubernetes-sigs/kueue#13984
• fix(logging): use structured fields for V(3)+ logging and event messages kubernetes-sigs/kueue#13637
• cleanup(kueueviz): remove noisy console.log and error output from fro… kubernetes-sigs/kueue#13983
• test: standardize and consolidate nodeEventsPredicate tests kubernetes-sigs/kueue#13603
• fix(debugger): prevent signal handler leak on context cancellation kubernetes-sigs/kueue#14011
• fix(kueuectl): fix grammar and formatting in list pods help text kubernetes-sigs/kueue#14019
• fix(webhook): correct typos and grammar in webhook error messages kubernetes-sigs/kueue#14018
• docs: fix issue number for tainted-node eviction in README roadmap kubernetes-sigs/kueue#13981
• docs: fix ProvisioningClassDetails typo in ProvisioningRequest doc kubernetes-sigs/kueue#13980
• [release-0.18] fix(webhook): validate labels and annotations in Workload PodSets template metadata kubernetes-sigs/kueue#13777
• [release-0.19] fix(webhook): validate labels and annotations in Workload PodSets template metadata kubernetes-sigs/kueue#13776
• fix(webhook): validate labels and annotations in Workload PodSets template metadata kubernetes-sigs/kueue#13679
• docs: reorganize community tabs into Join Us and User Showcase kubernetes-sigs/kueue#13604

kubernetes-sigs/lws

• Validate generated LWS/Service name lengths at DisaggregatedSet admission kubernetes-sigs/lws#966
• fix: ignore unrelated StatefulSets in LeaderWorkerSet watch mapper kubernetes-sigs/lws#957
• fix: skip creating SubdomainUniquePerReplica headless service for deleting leader pod kubernetes-sigs/lws#947
• fix: propagate SubGroupPolicyTypeAnnotationKey to worker pod annotations kubernetes-sigs/lws#945
• webhook: reject LeaderWorkerSet replicas outside [0, 1000000] range kubernetes-sigs/lws#913
• webhook: reject maxSurge=0+maxUnavailable=0 in DisaggregatedSet kubernetes-sigs/lws#912
• docs: fix DisaggregatedSet nits from #811 review kubernetes-sigs/lws#911
• docs: add DisaggregatedSet documentation kubernetes-sigs/lws#811

Other kubernetes-sigs projects

• add plugin: tripwire kubernetes-sigs/krew-index#6107
• Add correlate plugin v0.1.2 kubernetes-sigs/krew-index#6078
• driver: propagate context in Start method kubernetes-sigs/dra-driver-cpu#237
• docs: enhance conformance page with feature details and clearer structure kubernetes-sigs/kube-agentic-networking#318
• docs: add Problem-gate (NPD) example using defaultStatus kubernetes-sigs/node-readiness-controller#317

Notable open PRs

• fix: restore Cohort hierarchy after rejected cycle updates kubernetes-sigs/kueue#13774
• fix(workload): cache RuntimeClasses in queue manager for workload resource adjustments kubernetes-sigs/kueue#13912
• fix(workload): return error from AdjustResources to prevent error silencing kubernetes-sigs/kueue#13681
• feat: implement KEP-715 In-Place Group Restart kubernetes-sigs/lws#936
• Extend Helm manifest synchronization beyond CRDs kubernetes-sigs/lws#953
• fix: resolve DRA ResourceClaimTemplates for CapacityBuffer virtual pods kubernetes-sigs/karpenter#3200
• feat: support LeastAllocated placement strategy for scheduling simulation kubernetes-sigs/karpenter#3201
• feat: make leader election lease duration configurable kubernetes-sigs/aws-load-balancer-controller#4842
• feat: add Programmed status condition to XAccessPolicy (#314) kubernetes-sigs/kube-agentic-networking#319

Issues authored

• DisaggregatedSet admission accepts names that generate invalid LWS and Service names kubernetes-sigs/lws#959
• Fix nil-pointer panics in LeaderWorkerSet webhook and controller under nil conditions kubernetes-sigs/lws#931
• Cache RuntimeClasses in queue manager for workload resource adjustments kubernetes-sigs/kueue#13911
• Cleanup: Simplify CPUInfoProvider interface by removing GetCPUInfos kubernetes-sigs/dra-driver-cpu#283
• enriched ctx thrown away in most nri/dra hooks, opID and other fields get lost for downstream calls kubernetes-sigs/dra-driver-cpu#236

[yankay]

HI @Dasmat13

Thanks for opening this request, and sorry for the back and forth here.

I spent some more time reading the Kubernetes community membership requirements https://github.com/kubernetes/community/blob/main/community-membership.md#requirements. My understanding is that the bar is not just “at least one merged PR”; the contributions should also demonstrate ongoing and active commitment, such as sustained KEP/design work, multiple PRs over several weeks to months, or complex technical PRs that involve close collaboration with the community.

Your work in LWS looks promising, and I really appreciate the contributions so far. However, I do not think it clearly meets that bar yet. I would suggest continuing to build a stronger track record in LWS through merged PRs, design discussions, reviews, and issue follow-ups. I would be happy to revisit sponsorship after that.

[Dasmat13]

Hi @yankay,

Thank you for taking the time to review my membership request and for clarifying the expectations. I appreciate the honest feedback.

I'll continue contributing to LWS through PRs, design discussions, and follow-up work to build a stronger track record. I look forward to contributing more and revisiting this in the future.

Thanks again for your guidance and support!

[Dasmat13]

/area github-membership