CatOps

​​For today’s Donations Monday, I would like to remind you about the foundation that we’ve been partnering with for DevOps Days Ukraine for years now.

UA Responders. Their specialization is medical equipment and such.

#donations #Ukraine

Always Be Ready to Leave (Even If You Never Do) is not about keeping your CV up-to-date or socializing with recruiters, as it may seem from the title. It’s a short article on work habits that would keep you more efficient and, probably, happy at work; even if these habits would eventually make it easier for you to quit, if you choose to.

#culture

It's been a while since we had simple how-to articles here. So, here you are:
How to enable the JMX port on Jenkins.

It's short and actionable, and you would be surprised to learn how many people use Jenkins till these days.

#ci #java #debug

A postmortem from Cloudflare for yesterday’s outage is now available.

tl;dr:
>>>
The issue was not caused, directly or indirectly, by a cyber attack or malicious activity of any kind.Instead, it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a “feature file” used by our Bot Management system. That feature file, in turn, doubled in size. The larger-than-expected feature file was then propagated to all the machines that make up our network.
<<<

Another interesting thing:
>>>
Unrelated to this incident, we were and are currently migrating our customer traffic to a new version of our proxy service, internally known as FL2. Both versions were affected by the issue, although the impact observed was different.
Customers deployed on the new FL2 proxy engine, observed HTTP 5xx errors. Customers on our old proxy engine, known as FL, did not see errors, but bot scores were not generated correctly, resulting in all traffic receiving a bot score of zero. Customers that had rules deployed to block bots would have seen large numbers of false positives. Customers who were not using our bot score in their rules did not see any impact.
<<<

So, if you were not affected yesterday, you know why now.

#postmortem #cloudflare

We don't know why Cloudflare is down - their status page is not so detailed as one of AWS.

However, you can still check out some books on Humble Bundle:

- Data engineering & data science by O'Reilly.
- Software architecture by Pearson.

#books #bundle

​​For today's Donations Monday, I'd like to ask you to donate to the administrative needs of the "Come Back Alive" foundation.

It takes tremendous effort to run a foundation like this, and despite they can, they do not take money for the operational needs from regular donations. Thus, it's important to help them cover those needs as well!

https://savelife.in.ua/en/donate-en/#donate-fund-card-once

#donations #Ukraine

A new issue of the CatOps Digest is here:

https://newsletter.catops.dev/p/catops-digest-2025-11-14

#digest #newsletter

Press F to pay respects.

>>> Ingress NGINX Retirement: Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.

Announcement page.

#kubernetes #nginx

For people nostalgic for on-premise setups, Dropbox reviled their new generation hardware setup and the challenges they face storing exabytes of data.

#on_prem

An interesting lab for an overengineered solution from AWS for Kubernetes workloads right sizing.

Should you implement it this way? I don't know. But maybe, you want to play with GitOps, AWS Bedrock and all that stuff.

Also, it's funny how they say in the beginning that having VPA and Goldilocks inside a cluster is an overhead and additional management burden and then propose to create a cluster in GHA runtime and use generative AI to address that.

#aws #kubernetes

​​For today's Donations Monday, I'd like to share with you a fundraiser for the Optic Dragons unit - a specialized FPV drone assault unit of the 92nd Separate Assault Brigade.

They're raising funds for optical fiber drones, spare parts for converting drones to fiber optics, and supporting combat vehicles of pilot crews. The unit has been redeployed to the Pokrovsk direction where the situation is intense and they need more drone reels for optical drones.

Direct donation link:
https://send.monobank.ua/jar/7D7whfQHfF

Card number: 4441 1111 2291 2961

#donations #Ukraine

An article by Charity Majors on why thinking of Observability in pillars is limiting.

I recall a similar article from the past about how Facebook does their observability. It’s somewhere here on the channel.

The core idea is to treat all the signals as universal wide events that would allow one to preserve all the context and not hop between different tools.

#observability

A book bundle that I wanted to post a couple of days ago, but forgot. So, here it is:

Linux for Professionals by Apress.

#books #linux

More follow-ups for the AWS outage (Azure outage didn't generate that much press).

Lorin Hochstein analyzes the postmortem from the complexity point of view and comes to quite interesting conclusions that you can absolutely apply to your incidents and postmortems as well.

tl;dr is that incidents (especially bigger ones) are often unique. So, when reasoning about the preventive measures, you need not only to prevent similar incidents, but also get prepared to handle incidents in general, because the next incident may be not the same as the present one.

#reliability #sre #aws

​​For today’s Donations Monday, I’d like to share with you a fundraiser for FPV drones from DeepState - a collective behind the close-to-real-time battlefield maps.

https://send.monobank.ua/jar/9AtiB8esqu

#donations #Ukraine

A new issue of the CatOps Digest:

https://newsletter.catops.dev/p/catops-digest-2025-10-31

#digest #newsletter

OneUptime has published their update after two years since moving from AWS.

It's an interesting read, and tl;dr is that they do not regret their decision at all. Although, they admit that they still use cloud for dev environments, cold storage, etc.

Here are a few points that I find interesting:

- Our workload is 24/7 steady / We still recommend staying put if your usage pattern is spiky or seasonal - right sizing is one of the major advantages of clouds that is often overlooked.
- We still recommend staying put if you lean heavily on managed services - this is another important point. Managed services add a lot of value to the clouds. It does seem a bit dumb to use AWS just like an expensive datacenter. On another hand, if you want to be able to do multi-cloud, hybrid-cloud, etc.; you have to make a deliberate decision to stay as much decoupled from cloud offerings as possible. It's a deliberate strategy that trades flexibility for immediate value.
- Ceph stack in production - I'm sure, Ceph evolved a lot through the years, but I still remember words of a colleague of mine from a long time ago: "We didn't lose the data, we just cannot retrieve it". Back then, we decided to keep on-premise installations with ephemeral disks and ship all the data that has to be preserved into AWS (it's not like there was a lot of data to preserve there, though).
- so we added Anycast ingress via BGP with our transit provider to cut traffic shifting to sub-minute and We PXE boot with Tinkerbell - ask on an interview about Anycast, and the same day you will get an angry post on Reddit about unreasonable questions and lowballing candidates, lol. Or maybe, it's just my pessimism speaking.

Anyway, use your best judgment before doing any rapid moves. BTW, this advice is generally applicable, and is not limited to the clouds vs dc discussions.

#aws #bare_metal

Reddit engineers made a long post about their DevEx survey, which they shared... on Reddit.

This is a nice read, if you'd like to learn how different companies evaluate developer productivity and satisfaction.

A few interesting points there:

- They don't use any specialized SaaS tools for this survey - only Typeform and Looker.
- The survey is quite long, but the adoption seems to be good.
- They include various topics into the survey, not just purely DX metrics, they also changed the name of the survey to reflect that.
- Teams can use the results on their own to calibrate their decisions.

#dx #reddit

A glimpse into the alerting infrastructure of Hugging Face - a repository for ML models and datasets.

This article has a bit of a "they made me write this for promotion" vibe, but it's still interesting to see what technologies other people use, even if they don't dig deep into any of them.

#observability

I don't know if you are involved into the promotions cycles in your company or participate in hiring, but I still want to share with you this article - On Hiring: Promote Stars, Not Strangers.

It is targeted towards managers, but you can easily apply the core idea of this article to any role or position in a company.

#culture