GKE Gateway adds native CORS support, moving policy management to infrastructure layer

·2 views

Google Cloud's GKE team has released native CORS support for GKE Gateway and Inference Gateway, addressing a long-standing gap that frustrated teams migrating from Ingress-Nginx. Previously, developers had to implement cross-origin resource sharing policies individually within each backend service, leading to redundant code, wasted compute on preflight requests, and inconsistent configurations across microservices. With the new feature, Google Cloud Load Balancing handles OPTIONS preflight requests directly at the network edge, injecting required CORS response headers before traffic ever reaches backend containers. Developers can now define CORS policies declaratively using a CORS filter in standard Kubernetes HTTPRoute manifests, with granular control over allowed origins, methods, headers, and credentials. The implementation follows the open-source Kubernetes Gateway API specification and is currently available in Preview.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Reaches Week 11 of #100DaysOfCode, Diving Into Spring Boot Microservices

A developer participating in the #100DaysOfCode challenge completed week 11 by transitioning from microservices theory to hands-on implementation using Spring Boot. Across days 66 to 68, they studied architectural concepts including Lambda Architecture, Conway's Law, and reactive microservices, exploring how organizational structure influences software design. On day 67, they began a new chapter focused on building microservices, covering topics such as Spring WebFlux, OAuth2 security, Swagger documentation, and Spring Boot Actuator. By day 68, they had set up a Spring Boot development environment and built and tested a simple microservice, also learning about HATEOAS and the HAL format for REST responses. The learner noted that backend engineering extends beyond writing code to encompass architecture, scalability, security, and monitoring.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

GitHub's 7-Hour Outage Was Worsened by a VS Code Copilot Retry Loop

GitHub suffered a 7-hour, 47-minute outage on August 17, 2026, affecting Git operations, Actions, Issues, Pull Requests, and Copilot services. The incident began when an Istio sidecar proxy hit its concurrency limit, but GitHub's autoscaling failed to detect the overload since it monitored the host application rather than the proxy. A bug in the VS Code Copilot extension compounded the crisis by triggering aggressive client-side token re-requests, pushing the Copilot Token Service from its normal 7,000–9,000 requests per second to between 70,000 and 100,000. GitHub CTO Vlad Fedorov acknowledged that backend errors set off a client-side retry loop that amplified traffic precisely when the infrastructure was trying to recover. Engineers have since identified retry budgets and backoff with jitter as the key fixes to prevent unbounded retry storms from turning minor outages into prolonged incidents.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DEV Writer With 67 Posts Invites Community to Share Who They Are and What They Build

A prolific DEV Community contributor with 67 published posts has stepped away from technical content to invite readers to introduce themselves and share what they are working on. The author shared personal details, including an upcoming role as an official coach at a Boston Celtics player-backed basketball camp at Brandeis University on September 12. They described their long-term technical focus as building Self-Correcting Systems — machines that can detect unexpected outcomes, explain their reasoning, and flag failures rather than conceal them. The author also outlined plans for a cybersecurity system designed to keep complex underlying processes transparent and controllable at the user level. Ultimately, they expressed a goal of founding a company with collaborators who prioritize human oversight and evidence-based thinking in AI development.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Audit a Mortgage Amortization Schedule Row by Row

Most borrowers and analysts accept mortgage calculator outputs without verification, but a structured audit approach can reveal rounding errors, compounding bugs, and rate-encoding mistakes. Every amortization row should contain five values: payment number, payment amount, interest portion, principal portion, and remaining balance, and these must reconcile precisely across rows. Three quick tests — checking that interest matches the monthly rate times the prior balance, that principal plus interest equals the scheduled payment, and that the final row closes at exactly zero — can catch the majority of calculation errors. Any mortgage calculator worth trusting must expose per-row principal and interest breakdowns that are exportable and reproducible from the original inputs. These auditing principles apply equally to standard fixed-rate loans and more complex structures involving extra payments, variable rates, or biweekly schedules.

0 comments Read more at DEV Community