Adrian Kuepker

The Site Reliability Engineering: How Google Runs Production System book is arguably one of the most prevalent and well-known SRE resources out there, but there are many other great options for folks looking to expand on their learning. We recently spoke to Google's Reliability Advocate, Steve McGhee, in our Humans of Reliability interview series. In addition to his interesting anecdotes on the early days of SRE at Google, and his journey to becoming a Reliability Advocate, he also shared a handful of his favorite SRE resources, which we compiled here into a list: https://lnkd.in/gpUVhyRa

16

We're hiring! Move Frogward with JFrog! https://join.jfrog.com/ Have you met your future coworker, Roni Sheaffer, CRO Chief of staff, at JFrog? Q: How would you explain your job to a 5 year old? A: Wow, okay. To a 5 year old, I would say: I'm working for the best company in the world. We're going to take over the world and make it better: We make it easier for companies and people to update their software and keep it secure. My job is to help the person that determines how we're going to approach our customers and sell our products. I have to make sure she is able to comfortably do her job, and everyone around her in the organization is taken care of and successful! Q: How are you able to kick so high?! A: I don't exercise much and actually am a very lazy person in that regard, but I was a dancer when I was young, so I think I'm just flexible. This kick is a visual metaphor to show we aim high and are set to get there! Q: What's your favorite JFrog memory? A: When COVID hit, we suddenly transitioned from working in the office five days a week to working from our homes, separating us from our colleagues during the pandemic. I heard someone knocking on my door and got a text message from my manager saying, “Good morning! I know what you need...” and I found a milkshake and brownies at my door. It was from JFrog and it was a really kind gesture in making me feel appreciated and taken care of. Q: Why would you encourage someone to work at JFrog? A: JFrog offers an environment for individuals to be the best versions of themselves. We provide conditions for continuous growth. Employees start with a clear job description but there is no limit to what they can become here. You get to work with admirable colleagues, get to be challenged, have the opportunity to express who you are, and get to keep growing! #JFrogLife

70

4 Comments

🎶 Lay your cards down, down, down, down and join us at ObservabilityCON on the Road in Dallas tomorrow! Don’t miss: 🔸 Demos on how to control costs and maximize value 🔸 The latest observability features 🔸 New features using AI/ML that'll optimize your observability practice 🔸 Getting technical questions answered by our experts #observabilitycon #observability #grafana

29

There is a disturbing trend in tech job listings lately, companies are asking for much much more for much less salary. When your list of responsibilities basically reads like a posting for a QE, SDET and DevOps role you’re not looking for one person you’re looking for 3. I understand that the current perception is that this is an employers market, but if you’re not getting the candidates you want perhaps look critically at your job posting. People are desperate for work but you CANNOT retain good talent if you expect them do the work of three people for less than market for one. Sometimes I feel like employers are setting themselves up for The Great Resignation part 2.

18

2 Comments

Tech CEOs, is your team struggling with execution speed? Time to unblock your flywheel. Better handovers and faster throughput. Comment "flywheel" below OR direct message me for a quick tool to map things out.

5

In Kubernetes, taints and tolerations are like traffic signals for pods and nodes. Taints ensure that workloads only land where they’re meant to, preventing resource overload or mismatch, while tolerations allow specific pods to bypass those restrictions. Think of it as making sure your app doesn't end up on a "busy" or "wrong" node! #k8s #Devops #Cynefo https://cynefo.com

2

The SLO Matrix GCE uses to track 30M SLOs Alex Palcuie, SRE Google, explains the SLO Matrix he built and the challenges he had to overcome to track 30 million SLOs. #observability #sre #engineering

4

Who won this year's AWS re:Invent when it came to offering the best merch? 👀 It might surprise you to know that every year, the most popular article we write about re:Invent isn’t on some cutting edge feature or service, but actually on what swag there was to collect! 🥳 It’s completely understandable—there’s something therapeutic about scrolling through a stream of pictures of the latest, glittery merch. 😎 Adam Ipsen, Pluralsight Senior Content Strategy Manager, was in attendance and reviewed over 400+ pieces of swag this week. 👏 Here's Pluralsight's list of the definitive winners and stand-outs. 👇 https://bit.ly/3ZKaeda #AWS #AWSreInvent

17

1 Comment

⚡ BFCM traffic is like a tsunami. Will your site sink or swim? Your pre-BFCM checklist: 1. Run load tests simulating multiples of your expected peak traffic 2. Set up auto-scaling for your cloud infrastructure 3. Implement real-time alerting (so you're not the last to know when things go south) Get more pre-BFCM prep tips in our FREE Holiday Readiness Guide we partnered up with Edgio on: https://lnkd.in/gCXigAJ3

10

JFrog and GitHub have strengthened their alliance with a unified dashboard, streamlining vulnerability tracking from source code to deployed binaries. Now, DevOps teams can seamlessly navigate between GitHub Actions Workflows and JFrog Artifactory repositories, with visibility into security scans, permissions, and identities. This bi-directional integration makes it easier to prioritize vulnerabilities and ensure software is secure at every step. https://bit.ly/3TnvjGo #swampUP2024 #DevSecOps

2

In Search and Rescue we have a saying "slow is smooth and smooth is fast". The same mindset can be applied to #SoftwareEngineering. Have urgency and bias towards action, but don't rush. Find the root cause. Fix it once. Fix it right. An extra few cycles now will make you faster in the long run.

2

1 Comment

Nathan, Senior Vice President, Engineering at Vultr, explains how to prevent tool sprawl in modern platforms. He outlines a core technology stack for production environments, with Kubernetes as the foundation, Argo CD for deployments, and Prometheus with Grafana for observability. Nathan emphasizes the balance between maintaining a stable production environment while allowing teams to experiment with new tools in development. Watch the full interview: https://ku.bz/hX9c94l8s This is a reaction to Hans' episode: https://ku.bz/SyPM8Ch43

33

1 Comment

What’s new at Gremlin: 3 new AWS-specific Detected Risks 💥 🚀 Availability zone redundancy checks if an Application, Network, or Gateway load balancer is mapped to multiple availability zones. 🚀 Cross-zone load balancing checks whether you have cross-zone load balancing enabled on this service, improving your application’s ability to handle the loss of one or more instances. 🚀 Deletion protection checks that your load balancer has the “deletion protection” flag enabled to avoid accidental deletion. Detected Risks are enabled by default and can quickly show teams risks unintentionally introduced through configuration drift and non-best practices—without running fault injection tests. Want to learn more? Head to the link to try out our AWS-specific tools for yourself- free for 30 days. https://lnkd.in/gsYecFv8

7

Don't miss this fireside chat on August 21 at 2 PM ET/11 AM PT designed for technology leaders responsible for Kubernetes management, efficiency, and cost optimization. Dieter Matzion, Sr. Cloud Governance Engineer at Roku, will join Andy Suderman, CTO at Fairwinds, and Emilia A’Bell, Chief Revenue Officer, Platform9 who will provide actionable insights to elevate your Kubernetes strategy. Register here: https://bit.ly/3AgmUOj #webinar #kubernetesmanagement #kubernetesefficiency #costefficiency #roku #kubernetesstrategy #kubernetes #managedkubernetesasaservice #devops #finops

1

Corporate IT has no place on the path to production. I see LOTS of portcos that hold onto shortcuts they took when they were small. Corp IT runs Jira, or email goes out through the corporate mail gateway. Call it technical debt if you like, and taking on technical debt makes sense when you're a startup. But when you've made it past that stage, it's time to pay it down. Corporate IT is incredibly valuable. I was the Director of IT before I decided to dedicate my career to production web operations. I knew my CDW rep very well. Corporate IT can handle: corporate email, Salesforce, Tableau, calendaring, Zoom, Dropbox, etc. Corporate IT cannot handle: production SMTP gateways, Jira, Confluence, GitLab, Launch Darkly, Datadog, Cloudbees, etc. I don't care in the slightest which actual vendors you use for these functions. I've seen corporate IT change SCMs to "save money" without any input from engineering and set the entire organization release schedules back by more than 8 months because it turns out that GitHub "runners" have security concerns. People have made changes to corporate email and suddenly customers no longer receive notifications, and no one in engineering knows why. Engineering (including Operations) is where the money is made in a software company, and they need to own the path to production. Think of it in terms of "chain of custody" considering the concern over supply chain attacks. In the chain of custody, we don't just let someone with completely different concerns handle evidence. Why would you? #devops #sre #engineering

63

11 Comments

[K8s Optimization Workshop]: Run Highly Reliable K8s Clusters at the Lowest Possible Cost with Anton Weiss & Matthew Parker The truth is, Kubernetes costs can easily spiral out of control if not optimized properly. There are many ways to reduce Kubernetes spend without sacrificing reliability or performance. You just need to know where to look. In this hands-on training, you'll learn: ✅ How to benchmark your cluster's resource utilization and spot waste ✅ Strategies for rightsizing nodes to reduce infrastructure costs ✅ Tools and techniques for optimizing pod resource requests and limits ✅ How to leverage spot instances and preemptible VMs to slash cloud bills ✅ Ways to eliminate resource contention and improve cluster stability And much more! We'll share real-world examples and concrete steps you can take to optimize your own clusters. You'll walk away with actionable tactics to cut Kubernetes costs without compromising reliability. Save your spot today! https://lnkd.in/d9-P5y9D #kubernetes #devops #sre #k8s

8

#AWS announced changes to their #EKS pricing structure, impacting how clusters are managed and optimized. A shoutout to Udi Hofesh from Komodor for his great article breaking down these changes. He offers a clear explanation of the new model and shares practical tips to keep your #Kubernetes clusters running smoothly and cost-effectively. Check out the full blog post here: https://lnkd.in/dwE2u_E8

28

2 Comments