Kubernetes Meet & Greet at KubeCon NA 2024

[kaslin]

Describe the issue

We’re gearing up for KubeCon + CloudNativeCon NA in Salt Lake City and we would love to have you at the Kubernetes SIG Meet & Greet Lunch & Learn! (formerly known as SIG Meet & Greet, formerly known as Meet the Kubernetes Contributor Community)

This time, the Kubernetes SIG Meet & Greet is at the Project Pavilion on Thursday, November 14 at 12:30pm to 2:30pm MST. Grab your lunch and come join the Kubernetes SIG Meet and Greet! Here it is on the KubeCon NA 2024 schedule: https://sched.co/1oUD0

If your SIG is interested in having a table, please comment on this thread. We will update this top post as time goes by with participating groups.

A preliminary list of potentially participating community groups is listed here (alphabetical by committee, then by SIG, then by WG). If no one signs up to represent a group, it will be removed from the list before the event:

SIG API Machinery - SIG Apps - SIG Auth - SIG Autoscaling - SIG CLI - SIG Cloud Provider - SIG Cluster Lifecycle - SIG Contributor Experience - SIG Docs - SIG etcd - SIG Instrumentation - SIG Kubernetes Infrastructure - SIG Network - SIG Node - SIG Release - SIG Scheduling - SIG Storage - SIG Testing - WG Batch - WG Data Protection - WG LTS - WG Policy - /assign @kaslin @Princesso @RA489 /sig contributor-experience /area contributor-summit /area eu-summit

[reylejano]

I'll be there for SIG Docs

[JimBugwadia]

Thanks @kaslin! I will be there for WG Policy along with @poonam-lamba and @sudermanjr!

[satrox28]

Hi Team,

Thanks for the initiative. I am interested and will join the SIG Cluster Lifecycle 😀.

Thanks & Regards Sathish Kumar.V

On Wed, Oct 16, 2024 at 8:42 PM Jim Bugwadia @.***> wrote:

Hi @kaslin https://github.com/kaslin - I will be there for WG Policy along with @poonam-lamba https://github.com/poonam-lamba and @sudermanjr https://github.com/sudermanjr!

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

[pohly]

I can cover SIG Testing, SIG Instrumentation/WG Structured Logging, and WG Device Management.

[xing-yang]

I'll be there for SIG Storage and WG Data Protection along with @saad-ali, @msau42, and @jsafrane.

[haircommander]

I'll be there for SIG node, and I presume others will as well (some combination of @mrunalp @dchen1107 @SergeyKanzhelev @kannon92 @ndixita and others)

[kannon92]

I can be there for wg-batch / sig-node. I will also be helping out here on the volunteer front so I'll be there.

[jmhbnz]

I can be there for SIG etcd :)

[enj]

I will be there for SIG Auth (and Kube SRC).

[fedebongio]

I will be there for SIG API Machinery

cc @jpbetz @deads2k @sttts

[danwinship]

I'll be there for SIG Network (and we'll probably turn it into our SIG Network meetup lunch as we've done in the past).

[aramase]

I will be there for SIG Auth

[jpbetz]

I've be there for SIG API Machinery

[elmiko]

happy to be there for SIG Cloud Provider

[ivanvc]

I'll be there for SIG etcd

[ritazh]

+1 for SIG Auth and Kube SRC cc @liggitt @deads2k

[nilekhc]

I will be there for SIG Auth

[alculquicondor]

I'll be there for WG Batch and SIG Scheduling

[shaneutt]

I'll join Dan there for SIG Network :+1:

[ryanzhang-oss]

I'll be there for the SIG mulit-cluster

[soltysh]

I'll be there for SIG Apps, SIG CLI and WG Batch

[ameukam]

I'll be there for SIG Kubernetes Infrastructure. cc @BenTheElder @upodroid

[BenTheElder]

I'll be there for SIG K8s Infra and SIG Testing cc @michelle192837 @aojea

[michelle192837]

I'll be there for SIG Testing!

[Priyankasaggu11929]

I'll be there for SIG Contributor Experience.

[Huang-Wei]

I'm be there for SIG Scheduling.

[skitt]

I’ll be there for SIG-Multicluster.

[palnabarun]

I'll also be there for SIG Contributor Experience.

[k8s-triage-robot]

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[jpbetz]

/close This event has happened. No point keeping a planning issue open.