Hello everyone. In Hubble 1.15 we added some new redaction features to remove sensitive information from the Hubble network flows output, and I'm going to run you through those three new features quickly. The first one we're going to look at is redaction of user information. When we make an HTTP request that includes basic authentication, for example admin with a password, and then look for that request, we can see it in base64, because that's how it works in HTTP requests, and we can decode that back into plain text. We can see that live in the terminal. Now what we're going to do is enable redaction of the user info and restart the pods. When we make that same request again, we now have the Hubble redacted value in the authorization field for that header. The next one we're going to look at is redacting an API key that comes from the sample application. Again, we can see that in clear text today when we look at the JSON output from the application. We're going to update that to redact the API key, and we can see that here in these new Helm values that we've pushed through while we wait for the pods to come back up. Now again, when we look for that flow, we can see that Hubble has redacted it. Finally, we've got the HTTP headers themselves. We're going to make a request and we're going to see some particular headers that we've added ourselves. Under the headers in the JSON schema we're looking at, we can see the tracestate header, and we can also see the X-Powered-By header from httpbin. We're going to configure Hubble to only allow three particular headers, and anything else will be denied. Once we update those Helm values and wait for the pods to restart, we make that same request again and observe it. We can see that pretty much all of the fields in the headers are redacted apart from the three that we allowed in that configuration. Really quick and easy to configure.