community/communication/slack-config
Kubernetes Prow Robot 8f6e1325d0
Merge pull request #7707 from shaneutt/shaneutt/add-slack-channels-for-sig-network
Add some slack channels for SIG Network
2024-02-14 17:25:56 -08:00
..
sig-architecture slack-config(enhancements): Update subproject owners 2021-11-11 15:17:48 -05:00
sig-cloud-provider slack: renamed provider-alibaba-cloud channel 2019-12-20 18:31:04 +09:00
sig-docs Add kubernetes-docs-bg slack channel 2023-03-21 10:40:10 +09:00
sig-network Add a KPNG announcements channel 2021-09-24 11:10:40 -04:00
sig-node Sidecar WG slack channel 2024-02-12 16:41:53 -08:00
sig-release update 1.29 RT Lead/Shadows/EA info in slack 2023-08-31 09:36:20 +05:30
sig-security Add Slack Channel - vSphere CSI Driver assessment 2022-12-20 18:07:07 -05:00
sig-storage Setting up a slack channel for sig-storage subproject kubernetes-cosi 2020-07-17 12:24:37 +00:00
sig-testing Add TestGrid channel under sig-testing 2022-06-17 16:04:36 -07:00
OWNERS Update slack approvers to match current team 2023-01-06 17:53:58 -08:00
README.md Rename kubernetes-sigs/slack-infra default branch 2021-04-01 15:19:20 -04:00
channels.yaml feat: add a slack channel for the KNI project 2024-02-07 09:39:29 -05:00
restrictions.yaml slack sig-node: add users and dra-dev group 2022-09-13 17:05:54 +02:00
template.yaml Add initial slack config 2019-04-11 16:14:45 -07:00
usergroups.yaml Add KCSEU2024 Comms Lead temporary to Contributor Communications 2024-02-03 23:55:44 +01:00
users.yaml Add KCSEU2024 Comms Lead temporary to Contributor Communications 2024-02-03 23:55:44 +01:00

README.md

Slack Config

YAML files in this directory control the state of Slack, via Tempelis. Updating a configuration file will result in Slack being updated once the change merges. If a change is not legal, a presubmit will fail.

Users

There is no safe, stable way to derive a specific Slack user from any human-readable identifier. Instead of using Slack IDs everywhere, a single mapping from GitHub usernames to Slack IDs is given in users.yaml. To reference a user, they must first be added to users.yaml.

Channels

Channels can be created by adding a new channel in channels.yaml. Channels should be sorted alphabetically. New channels will be created in accordance with the template specified in template.yaml.

Deleting channels is not permitted, but a channel can be archived by specifying archived: true, or unarchived by removing it (or specifying false).

To rename a channel, set its id property to its current Slack ID, then change the name.

A fully-specified channel looks like this:

- name: slack-admins # mandatory
  id: C4M06S5HS      # optional except when renaming
  archived: false    # optional for unarchived channels

Usergroups

Usergroups are pingable Slack groups. All members of a usergroup can be automatically added to certain channels. A usergroup must have at least one member. A usergroup can be removed by deleting it from the configuration.

Some usergroups (e.g. @test-infra-oncall) are managed by other tooling. To prevent Tempelis from trying to deactivate these usergroups, they can be included on the list and marked as external: true. Other usergroups should look like this:

- name: slack-admins               # mandatory, the pingable handle
  long_name: Slack Admins          # mandatory, the human-readable name
  description: Slack Admin Group   # mandatory, a description
  channels:                        # optional, a list of channels for members to auto-join
    - slack-admins
  members:                         # mandatory, a list of at least one member.
    - castrojo                     # member names must be listed in users.yaml.
    - katharine
    - jeefy
    - mrbobbytables
    - alejandrox1
    - jdumars
    - parispitmann
    - coderanger
    - idvoretskyi
    - idealhack