A curated list of public Telegram channels and groups (chats) dedicated to DevOps, SRE, and Platform Engineering. English language only.
- Not active: 💀
- 1000+ members: 🔥
- 5000+ members: 🔥🔥
- 10000+ members: 🔥🔥🔥
- Curated by the Learnk8s team:
- @Learnk8sNews 🔥 — tutorials, articles and news on Kubernetes.
- @KubernetesArchitect 🔥 — news and links on architecting and developing apps on Kubernetes.
- @K3sDaily — news and links on K3s.
- @sysadmin_tools 🔥 — sysadmin and DevOps tools, news and articles.
- @devops_sre_notes 🔥🔥 — articles and books for DevOps & SRE.
- @securedevops 🔥 — tools and books for DevOps, DevSecOps & SRE.
- @CatOps 🔥🔥 — news and notes about DevOps, SRE, and more.
- @prodevopsguy 🔥🔥 — daily DevOps-related tips, job interview questions, etc.
- @kubernative — Kubernetes and cloud native-related news, articles & tools for DevOps and SRE.
- @Kubesploit 🔥 — news and links on Kubernetes security curated by the Learnk8s team.
- @KubeCareers 🔥 — hand-picked Kubernetes jobs curated by the Learnk8s team.
- @r_devops — r/devops posts from Reddit.
- @kubelet — Kubernetes blog feed.
- @rss_kubernetes 🔥 — a feed from various Kubernetes-related projects' GitHub repos and blogs.
- @Learnk8s 🔥 — Kubernetes-related discussions curated by the Learnk8s team.
- @dockeren 🔥 — a chat dedicated to Docker.
- @azuredevopspro 🔥🔥 — discussing DevOps-related issues in Azure and more.
- @devops_lemons 💀 — a community of software engineers interested in DevOps and SRE.
- @terraform_cloud 🔥🔥 — HashiCorp Terraform.
- @werf_io — werf, a CI/CD CLI tool and CNCF project.
If you want to see other Telegram resources in this list, please open new PRs adding them. Follow these rules:
- Be sure your channel/group fits the requirements. It should:
- use the English language only,
- relate to the topics (DevOps, SRE, and/or Platform Engineering),
- be public (you don't need to join it to see the messages),
- have recent messages,
- not be overfilled with sponsored/biased/spam messages (including endless free offers, vague job offers, and so on).
- Find a proper category for your addition and make a brief description similar to the existing entries.
- Make a separate PR per each addition.
- All decisions on accepting new entries are at the repo maintainers' discretion.