Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create etcd-security@kubernetes.io group #7739

Open
ahrtr opened this issue Mar 3, 2024 · 7 comments · May be fixed by kubernetes/k8s.io#6542
Open

Create etcd-security@kubernetes.io group #7739

ahrtr opened this issue Mar 3, 2024 · 7 comments · May be fixed by kubernetes/k8s.io#6542
Labels
sig/etcd Categorizes an issue or PR as relevant to SIG Etcd.

Comments

@ahrtr
Copy link
Member

ahrtr commented Mar 3, 2024 •
edited

Describe the issue

Currently users can report etcd vulnerabilities via security@etcd.io (refer to here) which is hosted under etcd.io google workspace.

The pricing for the Google Workspace Business Standard subscription will change beginning March 19, 2024. So we (including sig-etcd leads, maintainers, K8s Steering Committee members @BenTheElder @mrbobbytables and CNCF staff @idvoretskyi) agreed to terminate the etcd.io Google workspace as long as we can find an alternative for the security@etcd.io.

So requesting to setup etcd-security@kubernetes.io (suggested by @BenTheElder ), to replace the security@etcd.io with etcd-security@kubernetes.io.

cc
@jmhbnz
@serathius
@spzala
@wenjiaswe
@mrbobbytables
@BenTheElder
@idvoretskyi

Tasks
Beta Give feedback
No tasks being tracked yet.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 3, 2024
@ahrtr
Copy link
Member Author

ahrtr commented Mar 3, 2024 •
edited

/sig etcd

@k8s-ci-robot
Copy link
Contributor

@ahrtr: The label(s) sig/sig-etcd cannot be applied, because the repository doesn't have them.

In response to this:

/sig sig-etcd

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/test-infra repository.

@ahrtr
Copy link
Member Author

ahrtr commented Mar 3, 2024

/sig etcd

@k8s-ci-robot k8s-ci-robot added sig/etcd Categorizes an issue or PR as relevant to SIG Etcd. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 3, 2024
@ahrtr
Copy link
Member Author

ahrtr commented Mar 7, 2024

Could you advise the next step? @mrbobbytables @BenTheElder

@MadhavJivrajani
Copy link
Contributor

@ahrtr I believe you'll have to PR it in, create a dir here for sig-etcd: https://github.com/kubernetes/k8s.io/tree/main/groups

After that, you can create a group in there similar to
https://github.com/kubernetes/k8s.io/blob/2a49f086c136c95eb219a4ba7a8c10f3839fc48a/groups/sig-security/groups.yaml#L2

And once the PR merges, the post submit should pick it up and create the group accordingly.

@ahrtr ahrtr linked a pull request Mar 7, 2024 that will close this issue
Open
@ahrtr
Copy link
Member Author

ahrtr commented Mar 7, 2024

Thanks @MadhavJivrajani . Just created kubernetes/k8s.io#6542

@mrbobbytables
Copy link
Member

sorry I missed this @ahrtr my notifications are 💩 for pings >_<
sounds like its moving forward though, and I'm cc'ed on the other thread 👍

spzala added a commit to spzala/etcd that referenced this issue Mar 16, 2024
@spzala
Use etcd maintainers ML for security related discussion
8a49779 
Temporary move to using etcd maintainers mailing list
from security@etcd.io.

Related,
kubernetes/community#7739 and
kubernetes/k8s.io#6542

Signed-off-by: Sahdev Zala <spzala@us.ibm.com>
@spzala spzala mentioned this issue Mar 16, 2024
Merged
@jmhbnz jmhbnz mentioned this issue Mar 28, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/etcd Categorizes an issue or PR as relevant to SIG Etcd.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add etcd-security@kubernetes.io group ahrtr/k8s.io
4 participants
@mrbobbytables @MadhavJivrajani @k8s-ci-robot @ahrtr