DevOps and Cloud Engineers

DevOps and cloud engineers: provider channels, Kubernetes help, CI/CD, incident war stories and certifications.

9 categories
40 channels
15 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

ONBOARDING

handbook
Which category is for what, how war stories are written, how study groups form.
conduct
No employer names in stories, no vendor shilling, no pasting production secrets.
pick-your-cloud
AWS, Azure, GCP, Kubernetes, and the Story and Cert ping roles.
ops-bulletin
Sessions, guests and changes to the server.

CLOUD PROVIDERS

aws
Services, IAM, networking and the bill.
azure
Services, identity, networking and the bill.
gcp
Services, IAM, networking and the bill.
other-clouds-and-bare-metal
Smaller providers, colocation and the servers under someone's desk.
cloud-cost-optimisation
Where the money goes and how you found out.
provider-status
Vetox posts provider status page updates here.

CONTAINERS AND KUBERNETES

docker-and-containers
Images, builds, registries and the container that works on your machine.
kubernetes-help
One thread per problem. Include the manifest, the events and what you already tried.
service-mesh-and-ingress
Ingress controllers, meshes, certificates and the timeout that was not yours.
gitops
Declarative delivery, drift and the reconcile loop.

CI-CD AND IAC

ci-cd-pipelines
One thread per pipeline problem. Tag the system, paste the failing step.
terraform-and-iac
Modules, state, drift and the plan you did not read.
secrets-and-config
Vaults, rotation, env vars and what should never be in a repo.
release-strategies
Blue-green, canary, feature flags and rolling back on a Friday.

OBSERVABILITY

monitoring-and-alerting
Metrics, dashboards and the alert that pages at 3 a.m. for nothing.
logging-and-tracing
Pipelines, retention, sampling and finding the one request.
sre-practices
SLOs, error budgets, toil and the runbook nobody updated.

INCIDENT WAR STORIES

war-stories
One thread per incident. No employer names. The system, the failure, the lesson.
postmortem-reviews
Post a write-up, get it critiqued: blameless, specific, actionable.
on-call-life
The pager, the rota, the burnout and the fixes that helped.

CERTIFICATIONS

certification-prep
One thread per track. Resources, practice exams, and tag it Passed when you do.
study-groups
Propose a track and a schedule. Sessions run in the Study Room.
exam-day-tips
Booking, proctoring, timing and what surprised people, maintained by mentors.
cert-wins
You passed. Say which one and how long it took. Mentions Cert Pings.

LOUNGE

ops-lounge
Everything that is not a question, a story or a job.
homelab
Racks, mini PCs, power bills and the cluster in the cupboard.
ops-jobs300s slowmode
One post per role: company, location, range, link. No agencies.
Ops Lounge
Incident Story Time
Study Room
Pairing
AFK

STAFF

staff-ops
Reports, Certified grants and the recruiter of the week.
report-review
One message per report: link, what happened, outcome.
guard-alertsHidden from @everyone
Vetox posts Auto-Mod, Anti-Raid and moderation logs here.
Ops Staff

Roles

FounderAdministrator
AdminAdministrator
ModeratorModerator
SRE MentorModerator
Certified
Engineer
Student
AWS
Azure
GCP
Kubernetes
Story Pings
Cert Pings
Muted

Overview

A server for the people who keep production running: platform engineers, SREs, cloud architects and the developers who got handed the pipeline. Cloud Providers gives AWS, Azure and GCP a channel each, with #other-clouds-and-bare-metal, #cloud-cost-optimisation because the bill is an engineering problem too, and a read-only #provider-status feed. Containers and Kubernetes has #docker-and-containers, a #kubernetes-help forum tagged Networking, Storage, Scheduling, Helm and Operators with a Solved tag, #service-mesh-and-ingress and #gitops. CI/CD and IaC holds a #ci-cd-pipelines forum tagged by system, #terraform-and-iac, #secrets-and-config and #release-strategies. Observability covers monitoring, logging and SRE practice. Incident War Stories is the category people join for: #war-stories is a forum tagged Outage, Near miss, Security, Cost surprise and Lessons, #postmortem-reviews is where members critique each other's write-ups, and #on-call-life is the support group. Certifications has a #certification-prep forum tagged by track with a Passed tag, #study-groups, a read-only #exam-day-tips and #cert-wins. The Lounge adds #homelab, #ops-jobs, an Incident Story Time stage and a Study Room. Staff are hidden.

When to use it

Your ops community has a single channel where a Kubernetes networking question, a Terraform state argument and a 3 a.m. outage story compete, and the people who could answer each have muted it. Splitting providers, containers, pipelines and observability into categories gives each question the readers who chose it, turning incidents into a tagged forum makes them the searchable library they should be, and a certification track with a Passed tag gives studying a visible finish line.

What makes it different

#kubernetes-help is a forum tagged Networking, Storage, Scheduling, Helm and Operators, with a Solved tag.
#war-stories is a forum tagged Outage, Near miss, Security, Cost surprise and Lessons, so incidents become a library.
#postmortem-reviews is for critiquing each other's write-ups, separate from telling the story.
#certification-prep is tagged AWS, Azure, GCP, Kubernetes and Terraform with a Passed tag, next to #cert-wins.
AWS, Azure and GCP each get a channel, plus #cloud-cost-optimisation because the bill is an engineering problem.

Recommended Vetox setup

Self-Roles
Post Self-Roles in #pick-your-cloud for AWS, Azure, GCP and Kubernetes plus Cert Pings and Story Pings, so a new war story or study group reaches the people who asked.
Reminders
Schedule a Reminder in #study-groups every Sunday evening with the week's chapter, and one before each Incident Story Time session in #war-stories.
Notifications
Use Notifications with the RSS feeds of the provider status pages posted to #provider-status, so a regional outage appears in the server before someone asks whether it is just them.
Leveling
Grant Certified manually from #cert-wins, and use Leveling for Engineer so the role reflects months of answering in the forums rather than a title picked on join.
Auto-Mod
Enable Auto-Mod in #ops-jobs and #ops-lounge against link spam; recruiters and course sellers find ops servers first.

Questions

Should war stories name the company?

No, and #war-stories asks for that in the guidelines pinned at the top: describe the system, the failure and the lesson, not the employer. Members post more honestly when the story cannot be traced, and the lesson is what the next reader needs.

Why is Kubernetes a forum but the cloud providers are text channels?

Kubernetes questions are diagnostic: they carry manifests, logs and a resolution, and the tag tells a reader which subsystem is involved. Provider channels are conversational and a question there is usually about which service to use. Turn a provider channel into a forum if it fills with pasted logs.

How do people join a study group?

Take the Cert Pings role in #pick-your-cloud and watch #study-groups, where a member proposes a track and a schedule. Sessions run in the Study Room voice channel, and #cert-wins is where the pass gets announced and the Certified role is granted.

Common mistakes

One infrastructure channel for every provider, where the Azure answer to an AWS networking question is confidently wrong.
Letting incident stories scroll away in chat instead of a forum, which throws away the most valuable content the server produces.

Consider instead

Dev Team Internal The server is one company's on-call rotation rather than a public community of engineers from many teams.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages