Switch to Kubernetes colors for CRI streaming blog

Follow-up on #45821

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>

content/en/blog/_posts/2024-05-01-cri-streaming-explained.md

@@ -84,7 +84,7 @@ message PortForwardResponse {
 }
 ```
 
-Why is it implemented like that? Well, [the original design document](https://docs.google.com/document/d/1MreuHzNvkBW6q7o_zehm1CBOBof3shbtMTGtUpjpRmY)
+Why is it implemented like that? Well, the original [design document](https://docs.google.com/document/d/1MreuHzNvkBW6q7o_zehm1CBOBof3shbtMTGtUpjpRmY)
 for those RPCs even predates [Kubernetes Enhancements Proposals (KEPs)](https://github.com/kubernetes/enhancements)
 and was originally outlined back in 2016. The kubelet had a native
 implementation for `Exec`, `Attach`, and `PortForward` before the
@@ -111,6 +111,8 @@ sequenceDiagram
     participant kubelet
     participant runtime as Container Runtime
     participant streaming as Streaming Server
+    classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff;
+    class crictl,kubectl,API,kubelet,runtime,streaming k8s;
     alt Client alternatives
         Note over kubelet,runtime: Container Runtime Interface (CRI)
         kubectl->>API: exec, attach, port-forward
@@ -321,6 +323,8 @@ sequenceDiagram
     participant crictl
     participant runtime as Container Runtime
     participant conmon-rs
+    classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff;
+    class crictl,runtime,conmon-rs k8s;
     Note over crictl,runtime: Container Runtime Interface (CRI)
     crictl->>runtime: Exec, Attach, PortForward
     Note over runtime,conmon-rs: Cap’n Proto