{"id":"clm_1C3E7B8834DF","entity":"google-cloud","predicate":"feature_added","value":"Single-stack IPv6","value_json":{"feed":"google-cloud","item":"https://cloud.google.com/blog/products/networking/run-aiml-workloads-on-ipv6-only-gke-clusters/","tags":{"v":2,"ai":true,"by":"claude-haiku-5-5","on":"2026-11-19","themes":["compute_infra"]},"check":{"on":"2026-11-19","url":"https://cloud.google.com/blog/products/networking/run-aiml-workloads-on-ipv6-only-gke-clusters/","pages":1,"quote":"To help, today, we're announcing single-stack IPv6 on Google Kubernetes Engine (GKE), allowing you to run both nodes and pods on IPv6, without private IPv4 addresses.","outcome":"checked"},"evidence":"TL;DR: Single-stack IPv6 on GKE runs both nodes and pods without having to use private IPv4 addresses. Available in preview for Cloud TPU v6e and CPU node pools, including Axion, it works with DNS64/NAT64 to reach IPv4 endpoints. Long before they run out of compute or power, AI applications hit anot","extracted_by":"claude-haiku-5-5","primary_source":true},"valid_from":"2026-11-18","valid_to":null,"published":"2026-11-18","recorded":"2026-11-19","citation":{"plain":"AsOf. \"Google Cloud Platform feature added: Single-stack IPv6\", as of 2026-11-18. Claim clm_1C3E7B8834DF, https://asof.is/claim/clm_1C3E7B8834DF, accessed 2026-11-21. Source: https://cloud.google.com/blog/products/networking/run-aiml-workloads-on-ipv6-only-gke-clusters/.","url":"https://asof.is/claim/clm_1C3E7B8834DF","accessed":"2026-11-21"},"confidence":0.7,"status":"valid","assertable":true,"superseded_by":null,"supersedes":[],"first_seen_at":"2026-11-19T18:26:36.276367+00:00","updated_at":"2026-11-19T22:36:44.513177+00:00","sources":[{"url":"https://cloud.google.com/blog/products/networking/run-aiml-workloads-on-ipv6-only-gke-clusters/","tier":"primary","publisher":"Google Cloud","published_at":"2026-11-18T00:00:00+00:00"}],"evidence":{"by":"page-read","on":"2026-11-19","quote":"To help, today, we're announcing single-stack IPv6 on Google Kubernetes Engine (GKE), allowing you to run both nodes and pods on IPv6, without private IPv4 addresses.","url":"https://cloud.google.com/blog/products/networking/run-aiml-workloads-on-ipv6-only-gke-clusters/","excerpt":"TL;DR: Single-stack IPv6 on GKE runs both nodes and pods without having to use private IPv4 addresses. Available in preview for Cloud TPU v6e and CPU node pools, including Axion, it works with DNS64/NAT64 to reach IPv4 endpoints. Long before they run out of compute or power, AI applications hit anot"},"legend":{"dates":"valid_from: when the claim took effect (a period figure: the day its period closed). published: the earliest day a source on the record published it (a filing's filing date, a post's date; null when no source carries one). recorded: the day AsOf first held it. A figure can take effect weeks before it is published.","citation":"citation: how to cite the row (plain: one sentence with the value, its as-of date, the claim id and URL, the day answered and the primary source; url: the claim page; accessed: the day answered). APA and BibTeX forms are on the claim page.","why_not":{},"checked_by":{"page-read":"its source page states the value and the date, as read by an AI model"}}}