Creating a Mail List for Kubespray Notifications #8098
Conversation
k8s-ci-robot
added
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: yankay The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/S
|
HI @fabriziopandini @neolit123 Would you please help to review it :-) |
| @@ -480,6 +480,17 @@ groups: | |||
| - dlipovetsky@d2iq.com | |||
| - neolit123@gmail.com | |||
|
|
|||
| - email-id: k8s-infra-staging-kubespray@kubernetes.io | |||
There was a problem hiding this comment.
Could you assist the Kubespray team in establishing a notification mailing list for Kubespray-related communications?
in that case you might to scope and name the ML differently.
i'm proposing the name sig-cluster-lifecycle-kubespray
| - email-id: k8s-infra-staging-kubespray@kubernetes.io | ||
| name: k8s-infra-staging-kubespray | ||
| description: |- | ||
| ACL for staging kubespray artifacts. |
There was a problem hiding this comment.
put the correct description for purpose of the ML
| description: |- | ||
| ACL for staging kubespray artifacts. | ||
| settings: | ||
| ReconcileMembers: "true" |
There was a problem hiding this comment.
set to false or automation will only allow the listed members below to ever join.
There was a problem hiding this comment.
you might also want to set all these params
you can google search for what these google group params mean.
| ReconcileMembers: "true" | ||
| members: | ||
| - kay.yan@daocloud.io | ||
| - mg@max.gautier.name #VannTen |
There was a problem hiding this comment.
| - mg@max.gautier.name #VannTen | |
| - mg@max.gautier.name |
There was a problem hiding this comment.
Thanks @neolit123
Thank you very much for your detailed guidance. It has been modified.
yankay
force-pushed
the
create-mail-list-for-kubespray
branch
from
b566b83 to
212f01f
Compare
| WhoCanViewGroup: "ANYONE_CAN_VIEW" | ||
| WhoCanPostMessage: "ANYONE_CAN_POST" | ||
| WhoCanJoin: "ANYONE_CAN_JOIN" | ||
| MessageModerationLevel: "MODERATE_ALL_MESSAGES" |
There was a problem hiding this comment.
this means you have approve all messages from members or they cannot be posted.
are you sure about this?
There was a problem hiding this comment.
i think you might want to use the same settings as these for a general-purpose ML.
There was a problem hiding this comment.
Thanks @neolit123
Thanks for your patient guidance. It has been changed.
yankay
force-pushed
the
create-mail-list-for-kubespray
branch
from
212f01f to
4f78c00
Compare
| WhoCanModerateContent: "OWNERS_AND_MANAGERS" | ||
| MembersCanPostAsTheGroup: "false" | ||
| ReconcileMembers: "false" | ||
| members: |
There was a problem hiding this comment.
| members: | |
| owners: |
one final thing to change ^
There was a problem hiding this comment.
Thank you again, @neolit123. It has been changed.
Signed-off-by: Kay Yan <kay.yan@daocloud.io>
yankay
force-pushed
the
create-mail-list-for-kubespray
branch
from
4f78c00 to
b907fef
Compare
| - email-id: sig-cluster-lifecycle-kubespray@kubernetes.io | ||
| name: sig-cluster-lifecycle-kubespray | ||
| description: |- | ||
| Group for Kubespray maintainers to receive CI system notifications. |
There was a problem hiding this comment.
but this is not what you had in the pr description?
there are different settings for groups that will only receive notifications and public groups that are for user conversations.
what is the actual purpose of this ML?
There was a problem hiding this comment.
The intent was for a private mailing list for the maintainers. What prompted that was missing a notification from the infra provider of our CI (Oracle Cloud Infrastructure) with a need for action, leading to unavailability of our CI cluster. (The notification was sent to a mail which appears to be cncf, probably the organization contact for project using CNCF credits ? Not sure). The notif system is configurable from their console.
I'm not sure how sensible we should consider the notifs, but we erred on the side of caution.
There was a problem hiding this comment.
ok, looks like i misunderstand and the OP did speak about notifications. sorry about that @yankay
in that case:
- please use exactly the same settings like
- name the ML sig-cluster-lifecycle-kubespray-alerts
- add your owners
The Kubespray maintainers team requires a dedicated mailing list to serve as an official point of contact for receiving notifications from service providers (e.g., CI systems), ref to https://kubernetes.slack.com/archives/CDQSC941H/p1746458606052179?thread_ts=1746431573.418909&cid=CDQSC941H .
Could you assist the Kubespray team in establishing a notification mailing list for Kubespray-related communications?