The mentorship experience

From day one, I was working closely with core maintainers, which made a huge difference in understanding the project. Instead of spending weeks trying to decode design decisions on my own, I was able to get direct context on architecture, trade-offs, and long term direction. The focus of my mentorship was adding chaos engineering support to kgateway through HTTP fault injection. The idea is to let platform teams deliberately inject failures, such as delays and aborts, into their traffic so they can validate how resilient their services are before those failures show up in production. My core deliverable was implementing fault injection support by extending TrafficPolicy, covering delay injection, abort injection with both HTTP and gRPC status codes, response rate limiting, and a per-route override to disable it.

Under the hood it maps to the Envoy HTTP fault filter, which is added to the filter chain disabled by default and enabled selectively per route or virtual host. This keeps the feature completely inert unless a policy explicitly opts in. The learning curve was still real. kgateway sits at the intersection of Kubernetes, Envoy Proxy, and the Gateway API, so even small changes often required understanding multiple layers of the system. But having a structured path and regular syncs kept the progress steady and focused.

Some of the key areas I gained a deep understanding of during the mentorship included: Understanding the internal architecture of the kgateway control plane Kubernetes Gateway API implementation within kgateway kgateway plugin architecture for extensible policy design Abstracting low-level Envoy Proxy configuration into developer facing policies kgateway policy merge implementation and merge strategies Community collaboration and open source development workflows What stood out most was how iterative and collaborative the process was.