Skip to content

Add #syself slack channel #8298

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

Merged
merged 1 commit into from
Oct 13, 2025
Merged

Add #syself slack channel #8298

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions communication/slack-config/channels.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -522,6 +522,7 @@ channels:
- name: surveys
- name: summit-staff
- name: suse-caasp
- name: syself
Copy link
Member

@mrbobbytables mrbobbytables Jan 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't really do channels for companies/products. If there was an explicit project under them like the cluster api one we do support that kind of thing.

Copy link
Contributor Author

@lucasrattz lucasrattz Jan 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Cluster API Provider Hetzner project is under the Syself entity. The commercial product has another name (Autopilot).

Since Syself is also responsible for other Kubernetes-related open-source projects, I think it makes sense to name the channel 'syself', much like the channels 'rancher' (which is hosting conversation around k3s, rke, and other projects), and the cloud provider channels, as Syself is also providing a cloud platform.

Copy link
Contributor

@guettli guettli Apr 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mrbobbytables Could you please take another look?
Syself maintains cluster-api-provider-hetzner, cloud-controller-manager-hetzner, and hrobot-go — all open-source projects related to Kubernetes.

It would be great to have a single channel to communicate with users and contributors.

Copy link

@janiskemper janiskemper May 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @mrbobbytables ,
Thanks a lot for reviewing this PR. I very much understand that you don't usually do channels for companies or products. However, I am sure that you want to treat us in a fair way and therefore I'd ask you to reconsider.
The previous comments already gave multiple examples for relevant open-source projects that users heavily connect to the name "syself". Additionally, we have a plan with which allows users to create Kubernetes clusters with production-grade configuration for free (underlying infrastructure costs have to be paid to the respective cloud provider). This, in my opinion, should be considered as a valuable contribution to the Kubernetes community.
Finally, there are many more examples of companies that have already channels in the Slack community under their name and without clear reference to an open-source project. To name a few: azure-aks, canonical-kubernetes, digitalocean-k8s, eks, hetzner, kube-aws, scaleway-k8s.
Summing up, I do believe that based on the previous decisions on the channels that were allowed, it must be possible to add a channel with the name "syself", or something containing the name "syself".

- name: talk-proposals
archived: true
- name: tanzu-community-edition
Expand Down