Per-Service VM Tracing Starts With a Receiver and a Redeploy
Each VM service owner picks HTTP, gRPC or Zipkin, clicks Add variables and redeploy, and the platform saves the tracing env and triggers a revision.
Posts tagged cloudops.
zopdev writing tagged cloudops. Engineering and FinOps notes, post-mortems, and benchmarks.
VM Trace Stores: Wire Tempo, Jaeger or Zipkin to a Space
Add a Grafana Tempo, Jaeger or Zipkin endpoint in Settings, attach it to a VM space, and the platform probes for write and read before saving.
Container Limits for ZopDay VM Services, Refused Before Saving
A resource limit is only useful if you learn about its ceiling before you deploy. ZopDay VM services now take a CPU limit and a memory cap, both when the service is created, under Advanced settings,…
ZopDay VM Container Secrets Live in Your Cloud's Secret Manager
A secret is safe only if there is no later screen where it can be read. ZopDay VM services now let an org admin mark an environment variable as Secret, in a service's Settings and in Deploy a new…
Container Isolation on ZopCloud: One Network Per App
A shared VM is only fair if each tenant behaves as though it were alone on it. Apps on ZopCloud shared VMs now each run on their own network, so one tenant's app cannot reach another's. Outbound…
ZopDay VM Logs Now Ship to Your Own Observability Backend
Logs that only exist on the VM that produced them disappear with the VM. ZopDay VM spaces can now attach a logs backend that the customer owns, either Loki, VictoriaLogs or Datadog, right beside the…
Kubernetes and VM Basic Auth Needed One Endpoint, Not Four
A deployed service's web address with no password on it is one click away from being locked down. ZopDay puts that click right next to the address itself: an admin clicks a lock icon, and the service…
ZopDay's Kubernetes Service Cards Show Why a Pod Isn't Running
A card that only tells you a service is running still leaves the actual question unanswered: running well, or running on borrowed time. ZopDay's project canvas used to show a single status per…
Kubernetes Pod Consolidation Fights Its Own Placement Defaults
A node sitting at 13% processor utilization is common on a cluster that's never repacked its own workloads, and it still costs exactly as much as a node running at capacity. ZopDay's new Pod…
ZopDay Observability Now Reads From a Backend You Choose
A VM's Observability tab used to answer one question: is the container still running. Not what it did five minutes ago. ZopDay adds that history: a VM space, and a ZopCloud shared space, can now send…
Namespaces Are the Tenancy Line. Your Cluster View Should Respect It.
In Kubernetes, the namespace is where multi-tenancy actually lives. Resource quotas stop there. Network policy stops there. RBAC stops there. Then someone opens a live cluster view and sees every…
VM Observability on Par With Kubernetes, Without SSH
VM services get debugged over SSH while pods get a live observability tab. A control-plane exec channel closes the gap across AWS, Azure, and GCP.
OOMKill Is the Next Lie: Why Kubernetes Memory Limits Are Hiding Your Latency Spikes
CPU throttling has a visibility problem that the Kubernetes community partially fixed. exposes the throttle. Grafana dashboards flag it. Engineers know to look for it.
The Autonomous Action Log: Auditing Every ZopNight Decision in Production
The Autonomous Action Log: Auditing Every ZopNight Decision in Production CloudTrail is excellent at recording what happened. A node group scaled up at 14:32:07. A pod restarted at 14:32:41. An alarm…
The Fargate Tax: Why Serverless Kubernetes Costs 38% More Past 200 vCPU-Hours
The Fargate Tax: Why Serverless Kubernetes Costs 38% More Past 200 vCPU-Hours Fargate is appealing because the pitch is clean: no AMI patching, no node group sizing, no cluster autoscaler tuning. You…
Kubernetes MTTR: From 43 Minutes to 9 With Structured Runbooks
Kubernetes MTTR: From 43 Minutes to 9 With Structured Runbooks The median Kubernetes incident takes 43 minutes to resolve. Eight minutes of that is the actual fix. The other 35 minutes is engineers…
Event Readiness: A Wizard for Pre-Scaling Infrastructure Before a Launch
A product team announces a new feature on Tuesday at 10:00 AM Pacific. The marketing email goes out at 09:55. By 10:01 the load balancer is seeing 8 times its baseline request rate. The autoscaler is…
Cross-VPC Datastore Connectivity: When VPC Peering Works and When You Need PSC
A team provisions a Cloud SQL Postgres instance in one GCP VPC and wants to connect it to a GKE cluster in a different VPC. The team's instinct, learned from AWS habits, is to set up VPC peering…
Live Kubernetes Visibility: 21 Resource Pages and the Crashloop Overview
A 500-pod cluster has one pod that restarted three times in the last 10 minutes. The operator on call does not know which pod. returns 500 lines of and a handful of interleaved through them. Finding…
ZopNight Atlas: Region-Aware Cloud Mapping (Globe + Canvas)
A multi-cloud dashboard usually starts as a flat list of resources. One row per resource: name, type, region, status. Easy to scroll, easy to filter, easy to forget that the region column is the most…
The $90k Observability Bill: Why Your Cardinality Limit Is the One Knob That Matters
The observability bill at a 50-engineer org goes from $8,000/month in year one to $90,000/month by year three. The growth never gets a budget review because each individual instrumentation change…
Stop the App Before the Database: Dependency-Aware Shutdown for Non-Prod Environments
A team writes the cron job that shuts non-prod down at 8 PM. The cron runs three commands in parallel: scale the EKS Deployments to zero, pause the Aurora cluster, stop the ElastiCache Redis nodes.…
What IAM Permissions Does a Cost-Optimization Tool Actually Need? An Honest Read-Only Scope You Can Defend in Security Review
A platform team starts a security review for a cost-optimization vendor. The vendor's onboarding doc asks for a CloudFormation template that creates a role with "to ensure all features work." The…
Pod Scheduling for the Frugal: How We Cut EKS Node Cost 31% Without Touching a Workload
A right-sized EKS cluster should not run at 40 percent node utilization. The pods declare requests that sum to 78 percent of node capacity. The cluster autoscaler provisions nodes to fit those…
Closed-Loop SRE for Kubernetes: Auto-Remediating Pod Crashloops Before the On-Call Pages
The 3am page is rarely about something that needs a human. The on-call gets paged at 03:14 because a pod has crashlooped four times in five minutes. They open Slack, look at the logs, see "OOMKilled"…
Kubernetes CPU Throttling Is Lying to You: Why Container Limits Bleed Latency
The dashboard says CPU throttling is at 0.5%. The p99 latency on that container says 30% of requests just lost 80 milliseconds to scheduling delay. Both numbers are correct. They are measuring…
eBPF Gives Kubernetes Full Network Visibility Without the Sidecar CPU Tax
Istio sidecars cost 0.5 vCPU per pod at idle. At 100 pods, you're paying for 50 idle vCPUs. eBPF moves observability into the kernel — one hook point per node, not per pod. Here's the architecture, the tools, and when you still need Envoy.
Golden Paths That Include Cost Guardrails: A Platform Engineering Playbook
Every service provisioned from a Backstage template starts with zero budget alerts, zero mandatory tags, and a dev environment that runs 24/7. The platform team didn't choose this — they just never added cost defaults to the template. Here's how to fix that.
ZopNight v2.0: The Control Layer Your Cloud Bill Has Been Missing
Most teams treat cloud waste as a reporting problem. It isn't. ZopNight v2.0 ships the full four-layer control stack: discovery, policy, audit, and action — across AWS, GCP, and Azure.
Multi-Region Disaster Recovery: What Your RPO/RTO Decisions Actually Cost
Every DR design decision has a precise dollar figure. Active-active vs active-passive, cross-region replication cadence, failover automation. Here is the full cost breakdown.
Why Kubernetes Cluster Autoscaler Loses to Karpenter After 6 Months in Production
Cluster Autoscaler works on day one. Six months in, you have 12 node groups, 30% idle capacity, and scaling incidents during traffic ramps. Here is what changes when you switch to Karpenter.
Closed-Loop Cloud Remediation: How Autonomous Policies Replace On-Call Runbooks
The average remediation event takes 47 minutes in runbook-driven ops. The fix takes 4. Closed-loop remediation eliminates the overhead — here's the full technical architecture and how to start with your first policy.
The Real Cost of a Service Mesh: Istio Sidecar Overhead in Production
Istio adds 50-100m CPU and 50-100Mi memory per pod at idle. At 100 pods that's 10 extra CPU cores. Here's the overhead math at scale, what you actually get for it, and when lighter alternatives make more sense.
Introducing ZOP: Your Trusted Partner in Cloud Simplicity
Discover how ZOP simplifies cloud management with enterprise-grade automation. Learn how we helped McAfee reduce deployment times by 40% and how our cloud-agnostic orchestration can transform your operations.
Get the weekly in your inbox.
One post a week. Sundays. No "10 ways to think about cloud" listicles, just the engineering and FinOps notes we'd want to read.