Operations | Monitoring | ITSM | DevOps | Cloud

Private cloud and on-premises infrastructure are different. I know this. I used the terms interchangeably anyway because I was trying to compress a pattern into one sentence. That was sloppy, but the underlying pattern still matters. Banks run Kubernetes differently from most other organizations. Not because every bank makes the same choices, but because similar constraints can produce a similar pattern.

The dashboards are red, the alerts are firing, and Slack has officially become a war room. Someone has asked, “Anyone else seeing this?” and 14 people have immediately responded with screenshots. Welcome to another day in distributed systems. The recent GitHub outage is a great reminder of how complicated modern applications have become. Services talk to services, infrastructure scales up and down, retries multiply traffic, and dependencies behave in ways nobody expected.

Kubernetes normally excels at preserving uptime during maintenance tasks, but it’s not always perfect. Even something as benign as consolidating nodes after a traffic spike could take your application offline if not done carefully. This is where PodDisruptionBudgets (PDBs) come in. In this blog, we’ll explain why PDBs are important, what the risks are of not implementing them, and how you can find out which of your own deployments are missing PDB definitions. ‍

Perplexity was a big name a few years ago. But, we haven’t heard much out of them lately. There are plenty of posts on social media criticizing Perplexity to that effect. One thing that the posts miss is that Perplexity is still the king of AI search. Google is giving it a run for its money with the AI previews on Google search, but Perplexity still wins out in several measurable ways.

Somewhere in most production setups there is a container that stays awake all week to do one job on Friday. Maybe it re-indexes a database. Maybe it runs a batch report, or a data migration that only matters at month end. Either way, the resources are billed for seven days. Task containers close that gap. They are ephemeral, API-triggered containers that spin up inside an Upsun Cloud environment, run exactly one command, and remove themselves when that command exits. Nothing sits idle between runs.

Google Cloud Functions is Google's serverless functions product, renamed Cloud Run functions in August 2024 and folded into the Cloud Run platform. You write event-driven code, Google runs it, and you pay per request, per vCPU-second, and per GiB-second after a free tier of 2 million requests a month. The catch: per-invocation billing scales your mistakes exactly as efficiently as it scales your product.

Supabase offers four plans: Free ($0, two projects, 500 MB database each), Pro ($25 per organization per month plus usage), Team ($599 per month, adds SOC 2 and SSO), and Enterprise (custom). The base fee is the floor, not the bill. Compute ($10+ per project), egress ($0.09/GB), storage, and monthly active user charges stack on top, so real production bills run $35 to $200 per month. In June 2026, a database company most CFOs had never heard of raised $500 million at a $10.5 billion valuation.

The most common reason to create an API key in CloudZero is to send data, such as AI telemetry or billing exports. Until now, that meant picking individual scopes from a list and hoping you chose the right ones. That works on day one. The problem is day ninety. Permissions on a key have always been a snapshot of the day you created it. A new AI telemetry endpoint ships in October, and a key created in August has no idea it exists.