A shared, always-current view of every platform streamline: who owns it, which stage it is in, and what is about to change for the teams that depend on it.
Last update posted . Subscribe to the feed and you will not have to come looking.
Landing within 60 days, or landed in the last 30
From 2 November the provider keys held by individual teams are revoked. Calls made directly to a provider will fail with a 401; calls through the gateway are unaffected.
Switching over is a base URL change and a different key. The quickstart has the exact diff for each SDK we support.
Production upgrades run in three waves starting 1 October. Any workload
still declaring networking.k8s.io/v1beta1 Ingress objects will fail to
deploy once its cluster is upgraded.
Run kubectl deprecations --context <your-cluster> to see whether you are
affected. The migration guide has the before-and-after manifests.
What you need to do
kubectl deprecations --context <your-cluster> against every cluster your team owns.networking.k8s.io/v1, using the before-and-after manifests.Secret scanning and push protection
If a push is blocked, the message names the file and line. Rotate the credential first, then remove it from the commit — do not just force-push over it, because the secret is already in the reflog.
Rolling out to the remaining repositories through October and November.
We will contact owning teams individually from October. If your pipeline is on the list and you think it should simply be deleted, tell us — that is often the right answer for pipelines nobody has run this year.
LLM gateway · AI Platform
From 2 November the provider keys held by individual teams are revoked. Calls made directly to a provider will fail with a 401; calls through the gateway are unaffected.
Switching over is a base URL change and a different key. The quickstart has the exact diff for each SDK we support.
Remote build cache · Developer Experience
Median CI build time on those repositories is down from 11 to 4 minutes.
Secret scanning and push protection · DevOps
If a push is blocked, the message names the file and line. Rotate the credential first, then remove it from the commit — do not just force-push over it, because the secret is already in the reflog.
Rolling out to the remaining repositories through October and November.
Data catalog · Internal Tools
Warehouse tables first; event streams and object storage follow. Personal data classification is being reviewed with Legal before anything is opened up more widely.
Kubernetes 1.31 upgrade · DevOps
Production upgrades run in three waves starting 1 October. Any workload
still declaring networking.k8s.io/v1beta1 Ingress objects will fail to
deploy once its cluster is upgraded.
Run kubectl deprecations --context <your-cluster> to see whether you are
affected. The migration guide has the before-and-after manifests.
What you need to do
kubectl deprecations --context <your-cluster> against every cluster your team owns.networking.k8s.io/v1, using the before-and-after manifests.