-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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.
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
Create [email protected]
group
#7739
Comments
/sig etcd |
@ahrtr: The label(s) In response to this:
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. |
/sig etcd |
Could you advise the next step? @mrbobbytables @BenTheElder |
@ahrtr I believe you'll have to PR it in, create a dir here for After that, you can create a group in there similar to And once the PR merges, the post submit should pick it up and create the group accordingly. |
Thanks @MadhavJivrajani . Just created kubernetes/k8s.io#6542 |
sorry I missed this @ahrtr my notifications are 💩 for pings >_< |
Temporary move to using etcd maintainers mailing list from [email protected]. Related, kubernetes/community#7739 and kubernetes/k8s.io#6542 Signed-off-by: Sahdev Zala <[email protected]>
Describe the issue
Currently users can report etcd vulnerabilities via
[email protected]
(refer to here) which is hosted underetcd.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 [email protected].
So requesting to setup
[email protected]
(suggested by @BenTheElder ), to replace the[email protected]
with[email protected]
.cc
@jmhbnz
@serathius
@spzala
@wenjiaswe
@mrbobbytables
@BenTheElder
@idvoretskyi
Tasks
The text was updated successfully, but these errors were encountered: