community SIG-Multicluster: Leadership Change

SIG/WG name:

SIG Multicluster

Onboarding Lead(s):

skitt

Offboarding Lead(s):

pmorie

Link to discussion:

https://groups.google.com/g/kubernetes-sig-multicluster/c/xhj2OnFO-8M

Prerequisites for new leads:

[X] Are a Kubernetes Org member
[X] Have completed the Inclusive Open Source Community Orientation course

Onboarding / Offboarding tasks:

[x] Updated sigs.yaml and associated generated files (ran make). NOTE: If offboarding, remember to add to emeritus.
[x] Updated OWNERS_ALIASES in kubernetes/org.
[ ] Updated milestone maintainers team in kubernetes/org.
[x] Checked for and updated any other potential teams in kubernetes/org.
[x] Updated OWNERS_ALIASES in kubernetes/enhancements.
[x] Updated OWNERS_ALIASES in kubernetes/k8s.io.
[ ] Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes (when applicable)
[ ] Updated membership of the leads mailing list
[ ] Updated membership for any other mailing list / groups.
[ ] Added to #chairs-and-techleads slack channel.
[x] Updated ownership of group leads mailing list.
[ ] Updated ownership of group mailing list.
[x] Updated ownership of group calendar.
[ ] Updated access/teams in 1password. (Contact ContribEx leads to complete)
[ ] Update permissions for the corresponding Youtube playlists. (Contact YouTube moderators)

Additional information:

No response

Labels:

/sig multicluster

PRs:

https://github.com/kubernetes/community/pull/7963
https://github.com/kubernetes/org/pull/5043
https://github.com/kubernetes/k8s.io/pull/6932
https://github.com/kubernetes/enhancements/pull/4749

Jul 02 '24 08:07 skitt

/cc @JeremyOT

Jul 02 '24 15:07 skitt

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

Nov 10 '24 15:11 k8s-triage-robot

/remove-lifecycle stale

Nov 11 '24 22:11 skitt

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

Apr 24 '25 17:04 k8s-triage-robot

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

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

/lifecycle rotten

May 24 '25 17:05 k8s-triage-robot

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

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

/close not-planned

Jun 25 '25 02:06 k8s-triage-robot

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

In response to this:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Jun 25 '25 02:06 k8s-ci-robot

/reopen

Jun 25 '25 08:06 skitt

@skitt: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Jun 25 '25 08:06 k8s-ci-robot

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

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

/close not-planned

Jul 25 '25 09:07 k8s-triage-robot

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

In response to this:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Jul 25 '25 09:07 k8s-ci-robot

/reopen

Jul 25 '25 09:07 skitt

@skitt: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Jul 25 '25 09:07 k8s-ci-robot

/remove-lifecycle rotten

Jul 25 '25 09:07 skitt