From cb2eec6f68a61c9939e0d08fc48d6cfb9b5efb40 Mon Sep 17 00:00:00 2001 From: lhajouji Date: Fri, 27 Dec 2024 19:49:06 +0100 Subject: [PATCH] adding clicktozoom Signed-off-by: lhajouji --- content/en/blog/_posts/2024-12-17-api-streaming/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2024-12-17-api-streaming/index.md b/content/en/blog/_posts/2024-12-17-api-streaming/index.md index 87224cc3a0..f0aa3791d2 100644 --- a/content/en/blog/_posts/2024-12-17-api-streaming/index.md +++ b/content/en/blog/_posts/2024-12-17-api-streaming/index.md @@ -19,7 +19,7 @@ This can be explained by the differing nature of resource consumption by a singl This situation poses a genuine risk, potentially overwhelming and crashing any kube-apiserver within seconds due to out-of-memory (OOM) conditions. To better visualize the issue, let's consider the below graph. -{{< figure src="kube-apiserver-memory_usage.png" alt="Monitoring graph showing kube-apiserver memory usage" >}} +{{< figure src="kube-apiserver-memory_usage.png" alt="Monitoring graph showing kube-apiserver memory usage" class="diagram-large" clicktozoom="true" >}} The graph shows the memory usage of a kube-apiserver during a synthetic test. (see the [synthetic test](#the-synthetic-test) section for more details).