<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CuraDevOps</title><link>https://curadevops.metacog.co.kr/</link><description>Recent content on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 11:00:57 -0500</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon Timestream for InfluxDB adds EventBridge state change events</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-amazon-timestream-for-influxdb-now-publishes-database-state/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-amazon-timestream-for-influxdb-now-publishes-database-state/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running Timestream for InfluxDB can replace API polling with EventBridge rules to automate responses to scaling completions, failures, and maintenance events; worth building into monitoring/alerting workflows this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS MCP Server adds OAuth 2.0 support for AI agent authentication</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-oauth-support-for-the-aws-mcp-server/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-oauth-support-for-the-aws-mcp-server/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> OAuth integration for the AWS MCP Server extends IAM governance to AI agents via standard OAuth flows, CloudTrail audit events, and token revocation APIs — worth understanding as AI agent infrastructure matures, but no operational change required today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AI agents can now authenticate to AWS using existing IAM policies and OAuth 2.0, which lowers the governance barrier for agentic automation — relevant context for teams evaluating AI agent adoption on AWS infrastructure.&lt;/li>
&lt;/ul></description></item><item><title>Claude Code AI agent destroys production DB via Terraform command</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-claude-code-wiped-our-production-database-with-a-terraform-c/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-claude-code-wiped-our-production-database-with-a-terraform-c/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This incident—an AI coding assistant given unconstrained Terraform access wiping a production database—is a concrete signal to audit and restrict AI agent permissions to production IaC state; plan to implement plan-before-apply gates, workspace isolation, and state-level protections before allowing any AI assistant to execute Terraform in production environments.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Useful cautionary context if CI pipelines integrate AI-assisted Terraform steps, but the incident originates from an interactive AI assistant with direct production access rather than a pipeline mechanism; shapes how to scope AI tool permissions in future pipeline designs.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This high-profile incident—145 upvotes, 158 comments—is a concrete risk signal for any org adopting AI coding assistants; evaluate and formalize org-wide policy on AI agent access to production systems, and mandate guardrails (dry-run gates, least-privilege IAM, human approval for destructive operations) as a standard before broader rollout.&lt;/li>
&lt;/ul></description></item><item><title>CNCF Data Storage in Cloud Native AI White Paper</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-the-cncf-data-storage-in-cloud-native-ai-white-paper/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-the-cncf-data-storage-in-cloud-native-ai-white-paper/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Useful reference for designing storage architectures that support AI/ML workloads on cloud-native infrastructure, but no operational changes required and nothing currently running is affected.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Shapes strategic thinking on how to architect platforms for AI/ML workloads at scale; no immediate decision or vendor action required.&lt;/li>
&lt;/ul></description></item><item><title>etcd v3.7.0 GA: RangeStream, v2store removal, protobuf overhaul</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-announcing-etcd-v3-7-0/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-announcing-etcd-v3-7-0/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> etcd is the Kubernetes control-plane datastore, so this GA minor release is directly relevant; evaluate adopting v3.7 this quarter, particularly if large result-set latency or v2store remnants are pain points — no forced-upgrade deadline exists yet.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> etcd 3.7 supported · etcd 3.6 supported&lt;/li>
&lt;/ul></description></item><item><title>GCP: BigQuery hybrid search disabled, Advanced Compute Images preview</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-july-09-2026/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-july-09-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Advanced Compute Images (Preview) offer pre-tuned AI/ML/HPC OS images with drivers and Slurm pre-installed, potentially simplifying GPU node provisioning; separately, BigQuery hybrid search has been temporarily disabled — check if any workloads depend on the VECTOR_SEARCH hybrid mode.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Grafana Cloud access control scaling patterns for multi-team orgs</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-how-to-scale-access-control-in-grafana-cloud/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-how-to-scale-access-control-in-grafana-cloud/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Useful reference for SREs managing Grafana Cloud RBAC as observability centralizes across teams, but no operational change required — no EOL, deprecation, or security anchor present.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Outlines a scalable access governance model for centralized observability platforms, relevant when evaluating Grafana Cloud as a standard or managing sprawl across cloud/on-prem data sources.&lt;/li>
&lt;/ul></description></item><item><title>Grafana extends Volkov Labs BI plugin maintenance through end of 2026</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-business-intelligence-plugins-for-grafana-a-support-update/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-business-intelligence-plugins-for-grafana-a-support-update/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Useful context for teams running Volkov Labs BI plugins on Grafana: the maintenance window is extended and Grafana 13 / React 19 compatibility is done, but no action is required now and the post-2026 path remains undefined.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If the org is standardized on Volkov Labs BI plugins, the finite maintenance window expiring at end of 2026 warrants a strategic review this quarter — engage Grafana Labs on long-term product direction or evaluate alternative BI visualization solutions before the commitment lapses.&lt;/li>
&lt;/ul></description></item><item><title>Green DevOps: Adding carbon measurement to CI/CD pipelines with Eco CI and Carmen</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-green-devops-why-carbon-measurement-belongs-in-your-ci-cd-pi/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-green-devops-why-carbon-measurement-belongs-in-your-ci-cd-pi/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Introduces an emerging practice of per-pod and per-pipeline emissions visibility, which could inform infrastructure sizing decisions, but no operational urgency and no signals anchoring an action today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Eco CI and Carmen are wirable into existing GitLab pipelines today as lightweight integrations, worth evaluating as a team sustainability metric, but no deprecation, supply-chain risk, or deadline makes this actionable now.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Relevant for teams building ESG or sustainability reporting into engineering KPIs, but no licensing change, cost impact, or vendor risk forces a strategic decision — shapes future golden-path thinking only.&lt;/li>
&lt;/ul></description></item><item><title>ingress-NGINX retirement: migrate off the retired SIG Network controller</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-navigating-the-ingress-nginx-retirement/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-navigating-the-ingress-nginx-retirement/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> ingress-nginx reached end-of-life in March 2026 (now four months past); remaining on it means exposure to unpatched CVEs in a critical ingress path with no upstream fixes coming. Audit clusters for ingress-nginx usage and complete migration to a maintained alternative (Envoy Gateway, Ingress-NGINX from F5, Traefik) immediately.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> The SIG Network ingress-nginx controller is retired, making any org standardized on it subject to growing unpatched CVE exposure with no remediation path; this warrants a brief to leadership and a decision on a replacement ingress standard before the vulnerability surface widens further.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item><item><title>rocketplaneIO: self-hosted AI SRE copilot with eBPF for Kubernetes</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-olemeyer-rocketplaneio-126/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-olemeyer-rocketplaneio-126/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> An early-stage open-source project offering zero-instrumentation eBPF observability and LLM-driven remediation for Kubernetes is worth evaluating, but no GA signal or enrichment data exists to justify adoption planning yet.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Terraform CDK future direction discussed on HN</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-the-future-of-terraform-cdk/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-the-future-of-terraform-cdk/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Teams using CDKTF for IaC should read this discussion to gauge whether HashiCorp/IBM intends to maintain it long-term; no deprecation date in signals, so no action required now.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Against the backdrop of HashiCorp&amp;rsquo;s BSL relicensing and IBM acquisition, a high-signal HN discussion on CDKTF&amp;rsquo;s direction is a prompt to evaluate whether to continue standardizing on CDKTF or assess alternatives like OpenTofu CDK this planning cycle.&lt;/li>
&lt;/ul></description></item><item><title>Twenty years of DevOps: a critical retrospective</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-what-twenty-years-of-devops-has-failed-to-do/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-what-twenty-years-of-devops-has-failed-to-do/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A Honeycomb-authored retrospective arguing DevOps has fallen short of its goals — worth reading to pressure-test org strategy and cultural assumptions, though it carries a vendor perspective.&lt;/li>
&lt;/ul></description></item><item><title>Webernetes: Kubernetes ported to run in the browser (experimental)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-i-ported-kubernetes-to-the-browser/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-i-ported-kubernetes-to-the-browser/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> A novelty/educational project showing how far Kubernetes internals can be pushed; no production relevance, but interesting for understanding control-plane architecture.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Zero-Downtime Deployments with Docker Compose – No Kubernetes Required</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-zero-downtime-deployments-with-docker-compose-no-kubernetes/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-zero-downtime-deployments-with-docker-compose-no-kubernetes/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Describes a lightweight deployment pattern using Docker Compose that may be relevant for teams running simpler stacks; no pipeline changes required, but worth evaluating as a deployment pattern for non-Kubernetes environments.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>About CuraDevOps</title><link>https://curadevops.metacog.co.kr/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/about/</guid><description>&lt;h2 id="what-this-is">What this is&lt;/h2>
&lt;p>CuraDevOps is a daily, AI-curated DevOps intelligence channel. Most DevOps
news tells you &lt;em>what was released&lt;/em>; CuraDevOps tells you &lt;strong>who should do what,
now&lt;/strong> — every item gets three independent verdicts, one per practitioner
persona:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Persona&lt;/th>
 &lt;th>Judged on&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Platform/SRE&lt;/strong> (Infrastructure/Cloud)&lt;/td>
 &lt;td>upgrades, migrations, EOL exposure, operational impact&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>CI/CD&lt;/strong> (Build/Release/DevEx)&lt;/td>
 &lt;td>pipeline changes, supply-chain integrity, build/deploy mechanics&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Leader&lt;/strong> (Platform/Eng Management)&lt;/td>
 &lt;td>toolchain strategy, licensing, vendor risk, cost&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="the-verdicts">The verdicts&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Verdict&lt;/th>
 &lt;th>Meaning&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Act&lt;/strong>&lt;/td>
 &lt;td>do or check something now (imminent EOL, dated deprecation, supply-chain compromise, exploited CVE)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Plan&lt;/strong>&lt;/td>
 &lt;td>review within the quarter (announced breaking changes, new GA capabilities, migrations)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Learn&lt;/strong>&lt;/td>
 &lt;td>worth knowing, no action required&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Skip&lt;/strong>&lt;/td>
 &lt;td>not published — marketing, routine patch releases, duplicates&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Items judged Skip for &lt;em>all three&lt;/em> personas are never published. A zero-Act day
is normal — genuine urgency is rare in DevOps, and this channel does not
manufacture it.&lt;/p></description></item><item><title>Corrections</title><link>https://curadevops.metacog.co.kr/corrections/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/corrections/</guid><description>&lt;p>Confirmed misjudgments are logged here permanently — the original post gets a
correction note, and the error stays on this page. Format:&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>YYYY-MM-DD — [post title]&lt;/strong> — what was wrong, what the verdict should have
been, and why the error happened.&lt;/p>&lt;/blockquote>
&lt;h2 id="log">Log&lt;/h2>
&lt;p>&lt;em>No corrections yet. If you spot a bad verdict, please
&lt;a href="https://github.com/jeonck/curadevops/issues">open an issue&lt;/a>.&lt;/em>&lt;/p></description></item></channel></rss>