Systems | Development | Analytics | API | Testing

*Kong API Gateway 3.16 is here: runtime log-level tuning, per-consumer plugin configs, credit/usage-based request blocking with the new Entitlement Enforcement plugin, and FIPS 140-3 compliance for regulated industries - all built for live production debugging and governance, no downtime or custom code required.*

We're pulling back the curtain on a project we've been working on for some time now: the next evolution of the Kong brand. You may have noticed some changes recently to our site, swag, or socials. But today it's official: we're announcing Kong's rebrand and introducing our new mascot, Karl. Without further ado, let's dig in. Along the way, we'll give some insight into the "why" behind it all, while looking back at how things have changed since the early days of Kong. We were the API connectivity company.

A shared Kubernetes cluster rarely belongs to one team. Payments runs checkout in one namespace, search runs search-api in another, and a risk team runs a scorer somewhere else. One Speedscale forwarder captures API traffic for all of them. Redacting that traffic before it leaves the cluster is what makes it safe to use for testing (the background is in The PII Testing Dilemma). Until now, that forwarder ran exactly one DLP rule. Every team that needed a field redacted had to edit the same JSON document.

Ask five engineers whether a test is "functional" or "integration" and you will probably get three answers. That is not because people are confused. It is because the same test can honestly be both. Here is the short version. Integration testing checks that components work together. Functional testing checks that the software does what the requirements say. One is about how the pieces connect. The other is about what the user gets.

In Under the Hood with Go TLS and eBPF, I left socket tracking as an exercise for later. The example used bpf_get_current_pid_tgid() and explicitly excluded concurrent TLS operations. Capturing plaintext was enough for that post. With rustls, later arrived: I could read the HTTP payload perfectly and still attach it to the wrong TCP connection. That’s a frustratingly convincing failure. The request looks right. The response looks right. The application works.