Ryan Geyer

I wrote a blog entry on how to run Plex as a rootless Podman container. https://lnkd.in/gyR-bgbe #plex #podman #quadlet #fedora

23

Forget YAGNI, the real advice is PPPPP: Probably gonna Phuck up Parsers, Protocols, and Permissions auth system? phucked up regexing your html? phucked up anything involving email? phucked up are computers involved at all anywhere? you're phucked just say no to making silicone think

38

6 Comments

Check out our next Expert Observability article by Kevin Scaldeferri on leveraging Custom Events. https://lnkd.in/gYTt-QJa #newrelic #observability #monitoring

22

Thank you so much to David Wynn for joining me on the most recent episode of the Building With People For People podcast to talk about observability, his journey, AI and more! Since today is Trace Tuesday (is it? sure!) check it out now!! #podcast #ai #observability #softwareengingeering

9

2 Comments

AuthN is easy, AuthZ not so much. These 45(!) questions will get you started 😅. Don't want to spend time answering the questions? Try out our Permit.io for yourself and see how easy it is to add AuthZ to any application.

17

1 Comment

We met with Brent Bai to discuss JuiceFS, an open-source high-performance, cloud-native, distributed file system. We covered: 🔸 JuiceFS architecture 🔸 Demo resources walkthrough 🔸 Installing JuiceFS 🔸 Performance benchmark 🔸 JuiceFS CSI driver for Kubernetes 🔸 Other CSI driver options 🔸 How to contribute Watch the demo here: https://lnkd.in/e-3PafrG

1

Are you fully aware of the state of your K8s clusters? 🤔 If you NEED to track your K8S to mitigate risks, avoid wasting cloud allocation, and increase performance efficiency, then you won't miss out on this FREE PerfectScale Kubernetes Health Check! For 30 days, you'll receive a comprehensive assessment of the cost-effectiveness and stability of your K8s environment, with expert assistance and insights to help you cut costs by 50% while proactively eliminating resiliency risks. With quick, meaningful results and dedicated optimization specialist support, this assessment is 100% FREE of charge and requires no long-term commitment. Install in minutes and start getting optimization insights instantly. Don't wait - take advantage of this opportunity and optimize your K8s clusters today! Check it out here: https://lnkd.in/dS2bDJ8M Asaf Kivity Raz Dotan Gabriel Ben-Harosh Hasson Orna Greatz Benbenishty Limor Rozilio Amir Banet Amichai L. Eli Birger Michael Sklyar Ziv Mandl Lilach Meidan Libby Affen Oren Assayag Lior Katz Nastya Brodsky 🇮🇱 #DevOps #PerfectScale #מטריקס #Matrix

20

ATTN: DevOpsDays Seattle attendees! Kate Goldenring's presentation 🌱 A Greener, Cost-Effective Cloud With Serverless #WebAssembly 🌱 starts in 10 minutes! Learn how Wasm may solve cold-start issues while reducing an app’s software carbon intensity: https://bit.ly/3UTO3yz

3

🎙️ What happens when you get Liz Rice, #Kubernetes, and a toaster in the same #GiantConversations episode? Pure magic. ✨ Tune in as we dive deep into the world of #cloudnative, #eBPF, and unexpected kitchen appliances with Isovalent's finest. 😉 https://lnkd.in/guZ_tecF

9

In this episode of the .NET Core Podcast, @john_kattenhorn discusses using Temporal SDK to orchestrate success in distributed systems and enhance security and simplicity in managing complex workflows. https://lnkd.in/gJFfdpMz

1

Transparency for me but not for thee? This is almost never the issue. The real issue is, WHY?! Why are engineers taking too long? Why do sales people sell things that don't exist? Why don't people understand what the various tools and features do? I always find it interesting that people hate to ask the sales people why they sell stuff that doesn't exist. Or why Support doesn't understand the tools. Or why does engineering take so long. If anything has taught me a harsh truth, it's under cover boss has shown me that top level management, IE the executives, don't see all the facts, or aren't given an understanding of the relevance to those facts. Team: We failed because of "B". Management: Ok, fix "B". Team: We have but it keeps showing up. Management: Why? Team: Because of "C". Management: What is C? I kept that very short, but it is exactly the pattern of what goes on. The small pebble has a ripple that distorts and distracts everything. This leave no one who can see the origin to understand why some of these ripples are small, vs large, vs giant. This is where a root cause analysis (RCA) is needed. The RCA, which is normally a part of Corrective Action Reporting (CAR), clearly digs through all of the layers to find the root cause, in the metaphor above, the pebble. Most people stop on their CARs when they get the RCA, however, the rest of the report is about how to prevent further incursions of disruptions. How many times can a pebble drop into the pool of water until someone finally puts a shelter over the pool to prevent these pebbles? That is where the corrective part of the CAR comes into place. It is designed to outline the actions to be taken to prevent new pebbles, and to create policy if needed. So CARs don't just answer "why", but "how is it resolved", and "who is responsible for permanent or long term resolution." This provides transparency to the problem and the resolution. It also opens the floor for discussion for completeness. This is the glass house part that is rarely implemented. Once the manager of the source of the issue has the report, they need to open for discussion the corrective action, and see if people find it complete, or deficient. If something is onerous in it's correction, the discussion should stop and become an edict, but options for corrections should be made. Once the corrections have been implemented, these reports should have an executive summary attached as a coversheet, and shared with top level management. Then when they hear that something is failing in process, they have the resolution plan on hand, and there is a means to measure for success. In this metaphor, there are no more pebbles dropped into the pool of water. However, this GREATLY improves that glass house transparency that they top level management has wanted and needed, so they can walk in wisdom. See additional notes in comment.

4

2 Comments

Learn about the challenges and solutions for scaling Calico in large Kubernetes environments. Key Insights 🚀 Scalability Problems: Learn about common issues in large Calico deployments. 🛠️ Architectural Fixes: Discover improvements in Typha and Felix. ⚡ Managing Restarts: Handle large-scale restarts efficiently. 📊 Better Metrics: Use enhanced metrics for monitoring and troubleshooting. 🏗️ Best Practices: Optimize Calico’s performance at scale. Watch the full session here --> https://lnkd.in/gDaq42W3 #kubernetes #k8 #calicocon

8

Is your XM Cloud application build failing? You might have some content missing! John Matthew Flores wrote up a nice guide on troubleshooting deployment and synchronization issues to debug the source of rendering host errors. Quick summary: 1️⃣ Use deployment logs from your host (like Vercel) 2️⃣ Use the XM Cloud Deploy platform to access RenderingHost logs 3️⃣ Look for GUIDs showing up instead of source paths for data sources or fields 4️⃣ Try to find the item with that GUID using Content Editor. You might need to check different environments to find where it's hiding! 5️⃣ If nothing is missing (or you installed missing content) and it's still broken, check if the content is published #Nextjs #Sitecore Full article on the Fishtank blog➡️

16

Are your files not getting replicated or synchronized because they’re stuck in the Distributed File System Replication (DFSR) backlog?  This popular but aging technology can easily turn a good day into a frustrating one. The good news is that Resilio has a highly reliable and easy fix to your DFSR woes. #Resilio #ActiveEverywhere #DFS #MicrosoftDFS #datacenter

2

Grafana Alloy is hella *metal*! 🤘 Looking to get started? Check out this demo video from the team and be sure to drop in our Grafana Community Slack #alloy channel if you have questions: https://bit.ly/3Q34GFi #grafana #oss #observability #opentelemetry #prometheus

101

3 Comments

A great engineering post by Matthew Castanien Upleveling at ZI is a long process and contains many wins like proper testing decommissioning via disable first to reduce blast radius in case something goes wrong (and you know usually it goes wrong 😅) Kudos for great tips how to make it safer on GCP

15

Absolutely love this! Please watch if you have time. I think this short video does a wonderful job briefly explaining the importance of the Cloud Native Computing Foundation (CNCF), which Taylor D. does a wonderful job describing. I also think it helps shed light on how community is likely to play an increasingly important role in (1) software development and (2) ecosystem development for the future, *especially* in the era of Cloud and AI!

8