DevOps&SRE Library

We prepared a dataset from the GH Archive that contains all the events in all GitHub repositories since 2011 in structured format. The dataset was uploaded into ClickHouse, where it contains 3.1 billion records. We redistribute it for research purposes and it can be downloaded at this direct link. This dataset can help answer almost any question about GitHub that you can imagine.

This article shows the usage of the dataset and offers insights into the GitHub ecosystem. It emphasizes how easy it is to play with data using modern tools.

In this course, we are focusing on building strong foundational skills. The course is structured in a way to provide more real life examples and how learning each of these topics can play an important role in day to day SRE life.

- Let computers do the boring parts
- Settle style arguments with a style guide
- Start reviewing immediately
- Start high level and work your way down
- Be generous with code examples
- Never say “you”
- Frame feedback as requests, not commands
- Tie notes to principles, not opinions
- Aim to bring the code up a letter grade or two
- Limit feedback on repeated patterns
- Respect the scope of the review
- Look for opportunities to split up large reviews
- Offer sincere praise
- Grant approval when remaining fixes are trivial
- Handle stalemates proactively

1. Review your own code first
2. Write a clear changelist description
3. Automate the easy stuff
4. Answer questions with the code itself
5. Narrowly scope changes
6. Separate functional and non-functional changes
7. Break up large changelists
8. Respond graciously to critiques
9. Be patient when your reviewer is wrong
10. Communicate your responses explicitly
11. Artfully solicit missing information
12. Award all ties to your reviewer
13. Minimize lag between rounds of review

In this post, I would like to share the incident management practices I have picked up over the years as an SRE at Linkedin that help me keep calm under pressure and effectively drive incidents to resolution.

How culture enabled a technology org to scale without a dedicated platform team.

ZeroSSL.com is now joining the (sadly) very small group of awesome CAs giving away free, 90-day certs via ACME.

In short: Linkerd doesn't use Envoy because using Envoy wouldn't allow us to build the lightest, simplest, and most secure Kubernetes service mesh in the world.

This document is going to describe how I manage my personal server in 2020. It will talk about

- Management of secrets with SOPS and a GPG key
- Automatic management of DNS record
- Configuration of Debian and installation of Kubernetes k3s
- Setup Nginx ingress with let's encrypt for automatic TLS certificate
- Deployment of postfix + dovecot for deploying an email server
- Install Nextcloud to get your personal cloud in the sky
- Putting backup in place
- Using Wireguard to create a private network and WsTunnel to bypass firewalls
- Adding a Raspberry Pi to the K3s cluster