<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/kubernetes/</link><description>Recent content in Kubernetes 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/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><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>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>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></channel></rss>