search

kubernetes-retired / funding

Funding requests for project infrastructure, events, and consulting.
Apache License 2.0
16 stars 13 forks source link

request: one-time $NNNUSD to fund Windows kernel-space proxy work in KPGN #31

Closed marosset closed 1 year ago

marosset commented 2 years ago

This project is well-scoped and @jayunit100 has volunteered to mentor / support any willing engineer to help get this finished.

caniszczyk commented 2 years ago

Awesome, was an LFX style mentorship considered for this type of work btw?

https://github.com/cncf/mentoring/tree/main/lfx-mentorship

On Mon, Apr 18, 2022 at 4:28 PM Mark Rossetti @.***> wrote:

  • Description: kube-proxy next-gen https://github.com/kubernetes-sigs/kpng / KPNG is a Kubernetes SIG-network subproject that is re-architecting the kube-proxy to improve maintainability and extensibility. The subproject has made some great progress for Linux but needs some dedicated engineering resources to finish support for the Windows kernel-space proxy implementation. This is the last major hurdle to overcome before SIG-network can focus on making KPNG the default kube-proxy in Kubernetes.

This project is well-scoped and @jayunit100 https://github.com/jayunit100 has volunteered to mentor / support any willing engineer to help get this finished.

-

Requesting SIG: SIG-Windows and SIG-Network

SIG approval:

Cost: 1 engineer for 3 months

Alternatives considered:

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/funding/issues/31, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIL633YC3HM5NZVBSCDVFXHW7ANCNFSM5TW5AYRA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Cheers,

Chris Aniszczyk https://aniszczyk.org

marosset commented 2 years ago

Awesome, was an LFX style mentorship considered for this type of work btw? https://github.com/cncf/mentoring/tree/main/lfx-mentorship

No, but that only because I didn't know about this. I can look into submitting a request for this!

marosset commented 2 years ago

Awesome, was an LFX style mentorship considered for this type of work btw? https://github.com/cncf/mentoring/tree/main/lfx-mentorship

No, but that only because I didn't know about this. I can look into submitting a request for this!

Hi @caniszczyk - I took a look at the LFX mentionship program and see that the 'Spring 2022' session is already planned. Does that mean we'd need to wait for the next session to have the proposal be considered for the program?

We are looking to get this work completed sooner rather than later if possible. I'll keep the LFX mentorship program in mind for future requests tho!

caniszczyk commented 2 years ago

You can add your idea here for LFX Mentoring, it's not live yet so you can get in :) https://github.com/cncf/mentoring/blob/main/lfx-mentorship/2022/01-Spring/README.md

Also Summer of Code is open now and you can PR your idea here as an example: https://github.com/cncf/mentoring/blob/main/summerofcode/2022.md

You'd have to do this ASAP for GSOC as applications close soon for ideas, I think your best bet is LFX Mentorships.

We can also potentially do an LFX Mentorship "off cycle" using CNCF funds but all up to you.

We're flexible here.

On Mon, Apr 18, 2022 at 5:03 PM Mark Rossetti @.***> wrote:

Awesome, was an LFX style mentorship considered for this type of work btw? https://github.com/cncf/mentoring/tree/main/lfx-mentorship

No, but that only because I didn't know about this. I can look into submitting a request for this!

Hi @caniszczyk https://github.com/caniszczyk - I took a look at the LFX mentionship program and see that the 'Spring 2022' session is already planned. Does that mean we'd need to wait for the next session to have the proposal be considered for the program?

We are looking to get this work completed sooner rather than later if possible. I'll keep the LFX mentorship program in mind for future requests tho!

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/funding/issues/31#issuecomment-1101803781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIK5UWF3ENF7OAZC7ZDVFXL2FANCNFSM5TW5AYRA . You are receiving this because you were mentioned.Message ID: @.***>

-- Cheers,

Chris Aniszczyk https://aniszczyk.org

marosset commented 2 years ago

You can add your idea here for LFX Mentoring, it's not live yet so you can get in :) https://github.com/cncf/mentoring/blob/main/lfx-mentorship/2022/01-Spring/README.md Also Summer of Code is open now and you can PR your idea here as an example: https://github.com/cncf/mentoring/blob/main/summerofcode/2022.md You'd have to do this ASAP for GSOC as applications close soon for ideas, I think your best bet is LFX Mentorships. We can also potentially do an LFX Mentorship "off cycle" using CNCF funds but all up to you. We're flexible here.

I'd like to know what @jayunit100 thinks since he'd be doing the mentoring :)

jayunit100 commented 2 years ago

If it's a commited resource I'm in ! But they would need to have some prior experience in k8s & really be commited . It's an advanced project.

Many folks have come and gone on this project it's not fun or easy to tackle and very niche .

parispittman commented 2 years ago

@caniszczyk do LFX interns come with prior experience in k8s? I don't think I've seen any and might need to go the contractor route since this is an important initiative

justaugustus commented 2 years ago

(Jordan + Tim have been assigned as liaisons for SIG Windows and SIG Network, respectively)

parispittman commented 2 years ago

https://docs.google.com/document/d/1ksvxHru2Df6w23jesnpGEdZAalZfRtjCbssMAdn7BrA/edit

liggitt commented 2 years ago

tagging in network / windows / kpng subproject leads for visibility:

1 engineer for 3 months

This is less than a single Kubernetes release cycle. Is this a realistic time period for this project?

This project is well-scoped

Is https://docs.google.com/document/d/1ksvxHru2Df6w23jesnpGEdZAalZfRtjCbssMAdn7BrA/edit or https://github.com/kubernetes/enhancements/pull/2094 the current state of the proposal? Is there a pointer to the deliverables expected? Without a lot of context, an implementable KEP clearly laying out the design / deliverables (and associated work like testing, etc) seems like it could be pretty helpful for defining a scope of work that could be used here.

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/funding/issues/31#issuecomment-1279418425): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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 issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.